Triple
T23582072
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bor Dinka |
E582230
|
entity |
| Predicate | capitalTownAssociation |
P69811
|
FINISHED |
| Object | Bor (town) |
—
|
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: Bor (town) | Statement: [Bor Dinka, capitalTownAssociation, Bor (town)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capitalTownAssociation Context triple: [Bor Dinka, capitalTownAssociation, Bor (town)]
-
A.
capitalCityAssociation
chosen
Indicates a relationship where one entity serves as the capital city of another entity, such as a country, state, or region.
-
B.
capitalCityInvolved
Indicates that a capital city participates in, is affected by, or plays a role in a specified event, process, or relationship.
-
C.
capitalCityObservedIn
Indicates that a particular capital city was observed, recorded, or identified within a specified context, location, or time frame.
-
D.
capitalOftenLocatedIn
Indicates that the capital city of a region or country is frequently, though not always, situated within a particular location or type of area.
-
E.
capitalCityBuildingOf
Indicates that a building is located in and associated with the capital city of a given political or administrative 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_69e248f8d8248190acd5aee77f0d1709 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b02cf4e0819094ff4e406cda270d |
completed | April 29, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f118c96a0081908a8ac98ef7e7e60c |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:40 p.m.