Triple
T16915273
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Decentralized Administration of Crete |
E410303
|
entity |
| Predicate | hasSeatInBuilding |
P68735
|
FINISHED |
| Object | administrative complex in Heraklion |
—
|
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: administrative complex in Heraklion | Statement: [Decentralized Administration of Crete, hasSeatInBuilding, administrative complex in Heraklion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSeatInBuilding Context triple: [Decentralized Administration of Crete, hasSeatInBuilding, administrative complex in Heraklion]
-
A.
hasSeatBuilding
chosen
Indicates that a seat (or seating area) is located within or belongs to a particular building.
-
B.
hasSeatAt
Indicates that an entity occupies or holds a place, position, or membership within a specific group, body, or location.
-
C.
hasSeat
Indicates that one entity possesses, provides, or includes a seat for another entity.
-
D.
hasSeatStatus
Indicates the current condition or availability state of a seat in a given context.
-
E.
hasSeating
Indicates that one entity provides or contains seating capacity or seating arrangements for another entity.
- 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_69d886c7b1e481908c3766dfa8c13458 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3ca4015648190989904ad7119c3be |
completed | April 18, 2026, 6:15 p.m. |
| PD | Predicate disambiguation | batch_69e32b9489408190bcb2ede567ff5bf9 |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:30 a.m.