Triple
T21477541
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mário Cravo Júnior |
E529900
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Cravo |
—
|
NE NERFINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Cravo | Statement: [Mário Cravo Júnior, familyName, Cravo]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Cravo Context triple: [Mário Cravo Júnior, familyName, Cravo]
-
A.
Cravo
chosen
Cravo is a Portuguese-language surname most notably associated with Brazilian sculptor and engraver Mário Cravo Júnior.
-
B.
Cravo Norte
Cravo Norte is a rural municipality and town in eastern Colombia known for its cattle ranching and location in the plains of the Arauca region near the Venezuelan border.
-
C.
Macaxeira
Macaxeira is a neighborhood in the city of Recife, Brazil.
-
D.
Cravinhos
Cravinhos is a municipality in the state of São Paulo, Brazil, known for its agricultural activities and proximity to the regional hub of Ribeirão Preto.
-
E.
Cachaço
Cachaço is a settlement located within the municipality of Ribeira Brava in Cape Verde.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69e0c459acb481909bb6ee452a0045c7 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9ea1951fc8190910f634327aa5c3f |
completed | April 23, 2026, 9:44 a.m. |
Created at: April 16, 2026, 6:20 p.m.