Triple
T29210552
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yavanas |
E740534
|
entity |
| Predicate | hadSettlementsIn |
P16159
|
FINISHED |
| Object | South 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: South India | Statement: [Yavanas, hadSettlementsIn, South India]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadSettlementsIn Context triple: [Yavanas, hadSettlementsIn, South India]
-
A.
hasHumanSettlement
chosen
Indicates that a location or area contains or is the site of a human settlement, such as a town, village, or city.
-
B.
hadSettlementFeature
Indicates that a settlement possessed or contained a particular physical or infrastructural feature.
-
C.
hasHumanSettlementAlong
Indicates that a human settlement is located adjacent to or distributed along the length of a specified geographic feature or route.
-
D.
hasFormerSettlement
Indicates that a location previously contained a settlement that no longer exists or is no longer inhabited.
-
E.
coveredSettlementWith
Indicates that one entity (such as a material or structure) physically covers or overlays a settlement.
- 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_69f07cba2f808190a2746477d4e8345b |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f66404c158819099a062b5ecf6c856 |
completed | May 2, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69f65c24f8b48190af81b575f3c15be5 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 12:11 p.m.