Triple
T29926995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bountiful Utah Temple |
E760107
|
entity |
| Predicate | totalFloorAreaSquareFeet |
P24212
|
FINISHED |
| Object | 104000 |
—
|
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: 104000 | Statement: [Bountiful Utah Temple, totalFloorAreaSquareFeet, 104000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: totalFloorAreaSquareFeet Context triple: [Bountiful Utah Temple, totalFloorAreaSquareFeet, 104000]
-
A.
hasFloorArea
chosen
Indicates that an entity possesses a specified amount of floor space as a measurable area.
-
B.
floorAreaFeature
Indicates a relationship where a specific feature or characteristic is associated with the floor area of an entity or space.
-
C.
roofArea
Indicates the total surface area covered by the roof of a structure.
-
D.
housingArea
Indicates the geographic or spatial area associated with a housing unit or residential property.
-
E.
floorAreaRelation
Indicates a relationship comparing or specifying the floor area associated with one entity in relation to another (e.g., size, allocation, or proportion of floor space).
- 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_69f224631674819080c8d089674f9f4f |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6df450014819099d118e5c2d697fa |
completed | May 3, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69f6de07836481908785cde9c511920b |
completed | May 3, 2026, 5:32 a.m. |
Created at: April 29, 2026, 6:16 p.m.