Triple
T27538647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Steel Building (informal, historical) |
E695167
|
entity |
| Predicate | refersToBuildingType |
P147423
|
FINISHED |
| Object | office skyscraper |
—
|
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: office skyscraper | Statement: [U.S. Steel Building (informal, historical), refersToBuildingType, office skyscraper]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refersToBuildingType Context triple: [U.S. Steel Building (informal, historical), refersToBuildingType, office skyscraper]
-
A.
refersToBuildingOn
chosen
Indicates that one entity explicitly references or designates a specific building as its subject or target.
-
B.
appliedToBuildingType
Indicates that something (such as a rule, measure, or classification) is specifically applicable to a particular type of building.
-
C.
intendedBuildingType
Indicates the type of building that something is planned or designed to be.
-
D.
containsBuildingType
Indicates that a location or area includes at least one building of the specified type.
-
E.
belongsToBuildingType
Indicates that something is classified as being of a particular building type.
- 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_69ef538608b081908b9f659bb09d5e0f |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc53f4f881908dcc698687bbb64d |
completed | May 3, 2026, 7:42 a.m. |
Created at: April 27, 2026, 1:29 p.m.