Triple
T8445080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teke Peninsula |
E199651
|
entity |
| Predicate | containsArchaeologicalSite |
P11933
|
FINISHED |
| Object | Pinara |
E325080
|
NE 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: Pinara | Statement: [Teke Peninsula, containsArchaeologicalSite, Pinara]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pinara Context triple: [Teke Peninsula, containsArchaeologicalSite, Pinara]
-
A.
Pinara
chosen
Pinara was an important ancient Lycian city in southwestern Anatolia, known for its rock-cut tombs and well-preserved ruins.
-
B.
Pinjar
Pinjar is a landmark Punjabi novel that poignantly portrays the human cost of the Partition of India, especially through the suffering and resilience of women.
-
C.
Pira-Yine
Pira-Yine is an indigenous language of the Arawakan family spoken by the Yine people in the Amazonian region of Peru.
-
D.
Piro
Piro is an alternate name for the Yine language, an indigenous Arawakan language spoken in Peru.
-
E.
Piro
Piro is a town in the Bhojpur district of Bihar, India, known as one of the district’s principal urban and commercial centers.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ca83170f9081909cd98f55614c6476 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe3138ee08190918cd82adbe2d9a1 |
completed | March 31, 2026, 3:06 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ce1dac8cb08190b74985a6ba3c938f |
completed | April 2, 2026, 7:41 a.m. |
Created at: March 30, 2026, 6:09 p.m.