Triple
T34160720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Achaea regional unit |
E876269
|
entity |
| Predicate | capitalOfRegionalUnitLocatedAt |
P35957
|
FINISHED |
| Object | Patras |
—
|
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: Patras | Statement: [Achaea regional unit, capitalOfRegionalUnitLocatedAt, Patras]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capitalOfRegionalUnitLocatedAt Context triple: [Achaea regional unit, capitalOfRegionalUnitLocatedAt, Patras]
-
A.
capitalOfRegionalUnit
chosen
Indicates that one entity serves as the administrative capital of a specified regional unit.
-
B.
capitalOfSubregionLocatedHere
Indicates that a place serves as the capital of a subregion that is geographically located within it.
-
C.
capitalOftenLocatedIn
Indicates that the capital city of a region or country is frequently, though not always, situated within a particular location or type of area.
-
D.
capitalOfReferencedRegion
Indicates that one entity serves as the capital city or administrative center of the region referenced by another entity.
-
E.
capitalCityLocatedInZone
Indicates that a capital city is geographically situated within a specified zone or 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_69f349ac987481908a8e6053f665bc8b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd67191cf88190b53ecbf5be3564e9 |
completed | May 8, 2026, 4:31 a.m. |
| PD | Predicate disambiguation | batch_69fd654fdaac81908e67e75194710f06 |
completed | May 8, 2026, 4:23 a.m. |
Created at: May 1, 2026, 1:54 a.m.