Triple
T8229914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treasury of Atreus |
E192262
|
entity |
| Predicate | hasInteriorPlan |
P41702
|
FINISHED |
| Object | circular tholos with side chamber off passage |
—
|
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: circular tholos with side chamber off passage | Statement: [Treasury of Atreus, hasInteriorPlan, circular tholos with side chamber off passage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInteriorPlan Context triple: [Treasury of Atreus, hasInteriorPlan, circular tholos with side chamber off passage]
-
A.
hasInteriorFeature
Indicates that an entity contains or includes a specific feature within its interior space.
-
B.
hasFloorPlanShape
chosen
Indicates that an entity has a specific geometric or structural configuration defining the shape of its floor plan.
-
C.
hasStreetPlan
Indicates that an entity possesses or is associated with a specific layout or design plan for its streets.
-
D.
hasPlan
Indicates that an entity possesses or is associated with a specific plan or course of action.
-
E.
hasPlanningConcept
Indicates that an entity is associated with, defined by, or governed by a particular planning-related concept or framework.
- 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_69ca82db5b90819085d1ad7c2e27bfcc |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7802417c81908837c31136c41a5c |
completed | March 31, 2026, 7:30 a.m. |
| PD | Predicate disambiguation | batch_69cb36b1dea0819091418072501e79c1 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:46 p.m.