Triple
T17133026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alexander Mosaic |
E415766
|
entity |
| Predicate | locatedInRoom |
P40
|
FINISHED |
| Object | exedra of the House of the Faun |
—
|
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: exedra of the House of the Faun | Statement: [Alexander Mosaic, locatedInRoom, exedra of the House of the Faun]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInRoom Context triple: [Alexander Mosaic, locatedInRoom, exedra of the House of the Faun]
-
A.
locatedIn
chosen
Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
-
B.
locatedInBuildingWithFeature
Indicates that something is located in a building that possesses a specified feature or characteristic.
-
C.
hasRoom
Indicates that an entity possesses, contains, or is associated with a specific room.
-
D.
locatedOnLevel
Indicates that one entity is situated on a specific floor or level within a multi-level structure or system.
-
E.
positionInChamber
Indicates the specific location or role an entity holds within a particular chamber or assembly.
- 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_69d886d15af4819092f92f8a129763e6 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3f02ba4cc8190b6f433e08e958d83 |
completed | April 18, 2026, 8:57 p.m. |
| PD | Predicate disambiguation | batch_69e3830192ac819091344a9e5a36c8c9 |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:36 a.m.