Triple
T25356860
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yenice |
E635845
|
entity |
| Predicate | principalLocalCenterOf |
P41403
|
FINISHED |
| Object | Çanakkale Province |
—
|
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: Çanakkale Province | Statement: [Yenice, principalLocalCenterOf, Çanakkale Province]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: principalLocalCenterOf Context triple: [Yenice, principalLocalCenterOf, Çanakkale Province]
-
A.
centralLocation
Indicates that one entity serves as the primary or central place associated with another entity.
-
B.
centerOfOrigin
Indicates the place or region where something (such as a species, product, idea, or movement) originally began or was first developed.
-
C.
centerOfMassLocation
Indicates the spatial position at which the total mass of an object or system can be considered to be concentrated.
-
D.
centerOfComputation
Indicates that an entity serves as the primary location or hub where computational processing or data processing activities are performed for another entity or system.
-
E.
isCentralLocalityOf
chosen
Indicates that a locality serves as the main or central place within a larger administrative or geographic area.
- 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_69e75a9b7cf481909f2dcdfb37d95ca7 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f49e0263e081909449045f434eac6c |
completed | May 1, 2026, 12:35 p.m. |
| PD | Predicate disambiguation | batch_69f49377411c8190b2188de444d76795 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 21, 2026, 1:36 p.m.