Triple
T37777841
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cândido Mariano da Silva Rondon |
E941737
|
entity |
| Predicate | hasPartOfNameIn |
P93248
|
FINISHED |
| Object | State of Rondônia |
—
|
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: State of Rondônia | Statement: [Cândido Mariano da Silva Rondon, hasPartOfNameIn, State of Rondônia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPartOfNameIn Context triple: [Cândido Mariano da Silva Rondon, hasPartOfNameIn, State of Rondônia]
-
A.
fullNameIncludes
Indicates that one entity’s full name contains another specified string or name component as a substring.
-
B.
hasOfficialNameContaining
Indicates that an entity’s official name includes a specified substring or sequence of characters.
-
C.
hasPartiallyNamedAfter
chosen
Indicates that one entity is partially named in reference to another entity, such that only a portion of its name derives from or honors the other.
-
D.
hasNameInFamily
Indicates that an entity is known or referred to by a particular name within the context of a specific family or familial group.
-
E.
hasInhabitantName
Indicates that a place or region is associated with the specific name used for its inhabitants (demonym).
- F. None of above.
Provenance (3 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_69f76ee4431881908f87e8892a9f39f3 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a0064f8efa48190956287f548a8057d |
completed | May 10, 2026, 10:59 a.m. |
| PD | Predicate disambiguation | batch_6a006471e75c8190adae99bd75e7411b |
completed | May 10, 2026, 10:56 a.m. |
Created at: May 3, 2026, 4:19 p.m.