Triple
T6057138
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Palazzo dei Conservatori |
E134940
|
entity |
| Predicate | hasFloorUse |
P68010
|
FINISHED |
| Object | museum galleries |
—
|
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: museum galleries | Statement: [Palazzo dei Conservatori, hasFloorUse, museum galleries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFloorUse Context triple: [Palazzo dei Conservatori, hasFloorUse, museum galleries]
-
A.
hasFloor
Indicates that one entity possesses, includes, or is associated with a particular floor or level within a structure.
-
B.
hasUpperFloorUse
Indicates that an entity’s upper floor is assigned or designated for a particular use or function.
-
C.
hasGroundFloorUse
Indicates that a building or structure is associated with a specific functional use assigned to its ground floor level.
-
D.
hasBasementUse
Indicates that a building or structure’s basement is used for a specified purpose or function.
-
E.
hasUpperFloor
Indicates that one entity possesses or includes an upper floor relative to another level or reference point.
- 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_69c00877b6d4819096b0e163728b73a3 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c0570d00e88190b2d8d596e40378d9 |
completed | March 22, 2026, 8:54 p.m. |
| PD | Predicate disambiguation | batch_69c049edc6f0819092ca620d9073ad26 |
completed | March 22, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69c04dbefd1081909795fe1a812b991a |
completed | March 22, 2026, 8:14 p.m. |
Created at: March 22, 2026, 4:09 p.m.