Triple
T30515549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kird |
E776554
|
entity |
| Predicate | regionOfReferencedGroup |
P66507
|
FINISHED |
| Object | eastern Anatolia |
—
|
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: eastern Anatolia | Statement: [Kird, regionOfReferencedGroup, eastern Anatolia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionOfReferencedGroup Context triple: [Kird, regionOfReferencedGroup, eastern Anatolia]
-
A.
regionReference
chosen
Indicates that one entity refers to, points to, or is associated with a specific region or area defined by another entity.
-
B.
refersToGroupAssociatedWith
Indicates that one entity makes reference to a group that is associated or linked with another specified entity.
-
C.
regionOfAssociation
Indicates a broader geographic or spatial area with which an entity is functionally, contextually, or organizationally associated.
-
D.
regionFrom
Indicates that something originates from, is derived from, or is associated with a particular geographic or administrative region.
-
E.
nativeRegionOfMembers
Indicates the geographic region from which the members of a group or organization originally come.
- 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_69f2249b23c4819087fa85496d92f43f |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fe1fd637c08190aa95cd2478c278cb |
completed | May 8, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69fe19344bb481909b5e2144155e4add |
completed | May 8, 2026, 5:11 p.m. |
Created at: April 29, 2026, 8:16 p.m.