Triple
T26453682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chakradharpur |
E665422
|
entity |
| Predicate | divisionKnownFor |
P110087
|
FINISHED |
| Object | coal transport |
—
|
LITERAL 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: coal transport | Statement: [Chakradharpur, divisionKnownFor, coal transport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: divisionKnownFor Context triple: [Chakradharpur, divisionKnownFor, coal transport]
-
A.
divisionAlsoKnownAs
Indicates that one division is alternatively referred to by another name or alias.
-
B.
segmentKnownFor
chosen
Indicates that a specific segment or portion of something is recognized or notable for a particular characteristic, feature, or association.
-
C.
knownIn
Indicates that an entity is recognized, acknowledged, or familiar within a particular context, domain, or group.
-
D.
divisionTitle
Indicates the formal name or title assigned to a specific division within a larger organization or structure.
-
E.
divisionAssociation
Indicates an organizational relationship where one entity functions as a division, branch, or sub-unit of another entity.
- 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_69ee883d5040819097dd154643005230 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f62d53ad58819080c5227c7a729d15 |
completed | May 2, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69f62c15952881908a5ea0c25904afec |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 12:07 a.m.