Triple
T14292897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2016 Emporis Skyscraper Award |
E354359
|
entity |
| Predicate | appliesToBuildingType |
P106537
|
FINISHED |
| Object | 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: skyscraper | Statement: [2016 Emporis Skyscraper Award, appliesToBuildingType, skyscraper]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToBuildingType Context triple: [2016 Emporis Skyscraper Award, appliesToBuildingType, skyscraper]
-
A.
appliedToBuildingType
chosen
Indicates that something (such as a rule, measure, or classification) is specifically applicable to a particular type of building.
-
B.
appliesToBuildingComplex
Indicates that something (such as a rule, condition, attribute, or action) is relevant or applicable to an entire building complex rather than to individual buildings or units.
-
C.
appliedToBuilding
Indicates that something (such as a process, treatment, regulation, or attribute) is directed toward, implemented on, or otherwise affects a building.
-
D.
containsBuildingType
Indicates that a location or area includes at least one building of the specified type.
-
E.
intendedBuildingType
Indicates the type of building that something is planned or designed to be.
- 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_69d8278e17088190b328c5a9d4be74ff |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de7179368081908117a9ccfbf94fd4 |
completed | April 14, 2026, 4:55 p.m. |
| PD | Predicate disambiguation | batch_69de2a8f81f08190af737e1654847aa6 |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:11 a.m.