Triple
T23654510
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Security Trust and Savings Building (Los Angeles) |
E584257
|
entity |
| Predicate | hasFloorUsage |
P68010
|
FINISHED |
| Object | commercial offices |
—
|
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: commercial offices | Statement: [Security Trust and Savings Building (Los Angeles), hasFloorUsage, commercial offices]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFloorUsage Context triple: [Security Trust and Savings Building (Los Angeles), hasFloorUsage, commercial offices]
-
A.
hasFloorUse
chosen
Indicates that a particular floor or level of a building is designated for a specific function, activity, or type of use.
-
B.
hasFloor
Indicates that one entity possesses, includes, or is associated with a particular floor or level within a structure.
-
C.
hasUpperFloorUse
Indicates that an entity’s upper floor is assigned or designated for a particular use or function.
-
D.
hasFloorFeature
Indicates that a floor possesses or includes a specific feature or characteristic.
-
E.
hasFloorRole
Indicates that an entity holds a specific role, function, or responsibility associated with a particular floor or level within a building or facility.
- 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_69e248ffc0888190ae23c4731eb8b7ac |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b35a513c8190a251fe2f55b23d7c |
completed | April 29, 2026, 7:29 a.m. |
| PD | Predicate disambiguation | batch_69f118d7903c8190bb590a71771e93af |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:49 p.m.