Triple
T29417795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dev |
E746070
|
entity |
| Predicate | notableRelativeCitizenship |
P204265
|
FINISHED |
| Object | India |
E1124
|
NE FINISHED |
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: India | Statement: [Dev, notableRelativeCitizenship, India]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableRelativeCitizenship Context triple: [Dev, notableRelativeCitizenship, India]
-
A.
notableRelative
Indicates that an entity has a relative who is notable or well-known, specifying that familial relationship.
-
B.
notableNationality
Indicates that an entity is notably associated with a particular nationality, often by origin, citizenship, or cultural identity.
-
C.
hasNotableHolderCitizenship
Indicates that the notable holder of something (e.g., a title, position, or award) possesses the specified citizenship.
-
D.
citizenshipRelation
Indicates a formal legal relationship in which one entity holds citizenship status in, or is a citizen of, another entity such as a state or country.
-
E.
notableRelativeType
Indicates the specific familial or relational role that a notable relative has in relation to the subject.
- F. None of above. chosen
Provenance (5 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_69f0a79f6d5c8190a350baed0157e06f |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_6a035b78140081908e451cb63d3c1c7c |
completed | May 12, 2026, 4:55 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a260c0860f8819080b3abe16ae748c6 |
completed | June 8, 2026, 12:25 a.m. |
| PD | Predicate disambiguation | batch_6a035af3d8f48190bf1f3741d374404e |
completed | May 12, 2026, 4:53 p.m. |
| PDg | Predicate description generation | batch_6a035b773898819099125a5efc239d3e |
completed | May 12, 2026, 4:55 p.m. |
Created at: April 28, 2026, 3:02 p.m.