Triple
T29837463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | INCOC |
E757692
|
entity |
| Predicate | representsLocationInCountry |
P194128
|
FINISHED |
| Object | India |
—
|
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: India | Statement: [INCOC, representsLocationInCountry, India]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: representsLocationInCountry Context triple: [INCOC, representsLocationInCountry, India]
-
A.
representsCountryLocatedIn
Indicates that a country is geographically or politically situated within a specified larger region, territory, or context.
-
B.
representsTerritoryLocatedOn
Indicates that a specified territory is geographically situated on or within the bounds of a particular landmass or larger territorial unit.
-
C.
meetsInCountry
Indicates that two or more entities have an in-person meeting that takes place within the specified country.
-
D.
likelyLocatedIn
Indicates that an entity is probably situated within or associated with a particular location, though not with absolute certainty.
-
E.
meetsInCountrySubdivision
Indicates that two or more entities meet or have a meeting within a specific administrative subdivision of a country (such as a state, province, or region).
- F. None of above. chosen
Provenance (4 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_69f224593f6c81908785a560fe659f58 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fd64bc86848190a49f451a8fc5cf1e |
completed | May 8, 2026, 4:21 a.m. |
| PD | Predicate disambiguation | batch_69fd5ff4a648819090756d90fd195d9a |
completed | May 8, 2026, 4 a.m. |
| PDg | Predicate description generation | batch_69fd64bb345c819096a35c72784a8ce3 |
completed | May 8, 2026, 4:21 a.m. |
Created at: April 29, 2026, 5:37 p.m.