Triple
T27169915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Antandrus |
E682878
|
entity |
| Predicate | modernNameNearby |
P8489
|
FINISHED |
| Object | Altınoluk |
—
|
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: Altınoluk | Statement: [Antandrus, modernNameNearby, Altınoluk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modernNameNearby Context triple: [Antandrus, modernNameNearby, Altınoluk]
-
A.
nearbyTownFormerName
Indicates that the nearby town previously had a different name, specifying its former name in relation to the current nearby town.
-
B.
modernNameOfArea
Indicates that one area entity represents the current or modern name of another area entity.
-
C.
modernNameOfServedSettlement
Indicates that the object is the current, modern name of the settlement that is or was served by the subject (e.g., a facility, infrastructure, or service).
-
D.
cityNowKnownAs
Indicates that a city has changed its name and specifies the new name it is currently known by.
-
E.
modernLocality
chosen
Indicates that an entity is located in, associated with, or corresponds to a present-day geographic or administrative locality.
- 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_69eefacf6e788190a75a64399d9e3109 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f6c49627908190b3553474c7c3072b |
completed | May 3, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f23ae081909a52801266063a3c |
completed | May 3, 2026, 3:41 a.m. |
Created at: April 27, 2026, 9:23 a.m.