Triple
T11549696
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rōmon gate |
E273857
|
entity |
| Predicate | hasUpperStoryUse |
P44317
|
FINISHED |
| Object | ceremonial space |
—
|
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: ceremonial space | Statement: [Rōmon gate, hasUpperStoryUse, ceremonial space]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUpperStoryUse Context triple: [Rōmon gate, hasUpperStoryUse, ceremonial space]
-
A.
hasUpperFloorUse
chosen
Indicates that an entity’s upper floor is assigned or designated for a particular use or function.
-
B.
hasUpperFloor
Indicates that one entity possesses or includes an upper floor relative to another level or reference point.
-
C.
hasGroundFloorUse
Indicates that a building or structure is associated with a specific functional use assigned to its ground floor level.
-
D.
hasFloorUse
Indicates that a particular floor or level of a building is designated for a specific function, activity, or type of use.
-
E.
hasFloorsAboveGround
Indicates that an entity (typically a building or structure) possesses a specified number of floors that are located above ground level.
- 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_69d6aae4dfa48190a3ab0b19a159a3c5 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d886e615b08190a072924329a94a6a |
completed | April 10, 2026, 5:13 a.m. |
| PD | Predicate disambiguation | batch_69d8087e57b48190a4c253dc0210f9d4 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:37 p.m.