Triple
T36130776
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Museum of the Bible |
E1045006
|
entity |
| Predicate | hasExhibitionFloorCount |
P141170
|
FINISHED |
| Object | multiple floors |
—
|
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: multiple floors | Statement: [Museum of the Bible, hasExhibitionFloorCount, multiple floors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasExhibitionFloorCount Context triple: [Museum of the Bible, hasExhibitionFloorCount, multiple floors]
-
A.
hasExhibitionFloors
chosen
Indicates that an entity (typically a building or venue) possesses one or more floors or levels designated for exhibitions or displays.
-
B.
hasExhibitionArea
Indicates that an entity includes or provides a designated space or area for exhibitions or displays.
-
C.
locatedInBuildingFloorCount
Indicates that one entity is located in or associated with a building characterized by a specific number of floors.
-
D.
hasExhibitionBuilding
Indicates that an entity possesses or is associated with a building specifically used for exhibitions or displays.
-
E.
hasObservationFloors
Indicates that an entity possesses one or more floors specifically designated for observation or viewing.
- 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_69f76e36a4508190b5bfc8f594272a4c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd3a69f1e08190a11aed015bff0858 |
completed | May 8, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_69fd39124180819080ca7911d3515d6d |
completed | May 8, 2026, 1:14 a.m. |
Created at: May 3, 2026, 4:08 p.m.