Triple
T5474974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Theatre of Dodona |
E122928
|
entity |
| Predicate | hasProtectiveWalls |
P44339
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Theatre of Dodona, hasProtectiveWalls, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProtectiveWalls Context triple: [Theatre of Dodona, hasProtectiveWalls, yes]
-
A.
hasOuterWall
chosen
Indicates that one entity possesses or is surrounded by an external enclosing wall that defines its outer boundary.
-
B.
hasBorderWallOrFence
Indicates that a physical barrier such as a wall or fence exists along the border between two entities.
-
C.
hasSideWalls
Indicates that an object or structure possesses side walls as part of its physical configuration.
-
D.
hasWallType
Indicates the specific kind or classification of wall associated with an entity.
-
E.
hasWallShape
Indicates that an entity possesses a wall whose form or outline matches a specified geometric or structural shape.
- 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_69bd46459ff48190823377457bcf7128 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd923465c88190ad9c1b75b268f7ca |
completed | March 20, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69bd91a58c448190904964a439045e05 |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:09 p.m.