Triple
T9274143
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lupanar of Pompeii |
E222900
|
entity |
| Predicate | hasGroundFloorRooms |
P87903
|
FINISHED |
| Object | 5 |
—
|
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: 5 | Statement: [Lupanar of Pompeii, hasGroundFloorRooms, 5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGroundFloorRooms Context triple: [Lupanar of Pompeii, hasGroundFloorRooms, 5]
-
A.
hasGroundFloor
Indicates that a building or structure includes a ground-level floor as part of its layout or design.
-
B.
hasFloorsAboveGround
Indicates that an entity (typically a building or structure) possesses a specified number of floors that are located above ground level.
-
C.
hasGroundFloorUse
Indicates that a building or structure is associated with a specific functional use assigned to its ground floor level.
-
D.
hasUpperFloor
Indicates that one entity possesses or includes an upper floor relative to another level or reference point.
-
E.
hasFloor
Indicates that one entity possesses, includes, or is associated with a particular floor or level within a structure.
- F. None of above. chosen
Provenance (4 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_69ca841ffe208190aa7bcffbef2f8379 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd0788e87c81909ccda40d94cc6705 |
completed | April 1, 2026, 11:54 a.m. |
| PD | Predicate disambiguation | batch_69cc7a537bbc8190baee71f556e52a7b |
completed | April 1, 2026, 1:52 a.m. |
| PDg | Predicate description generation | batch_69cc95597be081908ece2491dd2f0f74 |
completed | April 1, 2026, 3:47 a.m. |
Created at: March 30, 2026, 7:33 p.m.