Triple
T35781992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gallograeci |
E1034461
|
entity |
| Predicate | areaCorrespondsTo |
P137052
|
FINISHED |
| Object | modern central Turkey |
—
|
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: modern central Turkey | Statement: [Gallograeci, areaCorrespondsTo, modern central Turkey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: areaCorrespondsTo Context triple: [Gallograeci, areaCorrespondsTo, modern central Turkey]
-
A.
modernAreaCorrespondsTo
chosen
Indicates that a historical or former area is associated with, or has its equivalent in, a specified modern geographic or administrative area.
-
B.
areaDefinedAs
Indicates that one area is formally specified, delimited, or characterized in terms of another area or defining criteria.
-
C.
regionCorrespondsRoughlyTo
Indicates that one region approximately matches or aligns with another in location, extent, or boundaries, but not with precise or exact correspondence.
-
D.
areaComponent
Indicates that one area is a constituent or sub-area that forms part of a larger area.
-
E.
representedArea
Indicates that one entity serves as a representation or depiction of a particular area or region.
- 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_69f76e14a1e081908eddd57bd6fdb3be |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a226811481909691d0cea0c05b3a |
completed | May 3, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69f7a070e23881909a233370acb57384 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:06 p.m.