Triple
T12585521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pepsi-Cola World Headquarters |
E300446
|
entity |
| Predicate | hasFacadeSystem |
P105573
|
FINISHED |
| Object | curtain wall |
—
|
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: curtain wall | Statement: [Pepsi-Cola World Headquarters, hasFacadeSystem, curtain wall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFacadeSystem Context triple: [Pepsi-Cola World Headquarters, hasFacadeSystem, curtain wall]
-
A.
facadeFeature
Indicates that one element functions as a distinct architectural or design feature on the façade of another structure.
-
B.
hasAspectSystem
Indicates that an entity possesses or is associated with a particular aspect system, such as a structured set of characteristics, dimensions, or perspectives.
-
C.
hasLEDFacade
Indicates that an entity features a facade equipped with LED lighting or LED display technology.
-
D.
hasBaseSystem
Indicates that one entity is founded upon, derived from, or primarily operates using another entity as its underlying system or framework.
-
E.
hasPASystem
Indicates that an entity possesses or is equipped with a public address (PA) system.
- F. None of above. chosen
Provenance (4 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_69d7bde87b648190bcd0266e9efde098 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d954e6e20481908bca684c4b497c48 |
completed | April 10, 2026, 7:52 p.m. |
| PD | Predicate disambiguation | batch_69d95416cbd88190b2c65196162349bc |
completed | April 10, 2026, 7:48 p.m. |
| PDg | Predicate description generation | batch_69d954e351f88190869220d46e0ce282 |
completed | April 10, 2026, 7:52 p.m. |
Created at: April 9, 2026, 5:04 p.m.