Triple
T32335522
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tower 42 |
E826159
|
entity |
| Predicate | hasSkylineSignificance |
P110109
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Tower 42, hasSkylineSignificance, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSkylineSignificance Context triple: [Tower 42, hasSkylineSignificance, yes]
-
A.
isGloballySignificant
Indicates that something has importance, impact, or relevance on a worldwide scale rather than being limited to a local or regional context.
-
B.
hasSignificant
Indicates that one entity possesses or exhibits a level of importance, impact, or relevance that is notably large or meaningful in relation to another entity or context.
-
C.
skylineType
chosen
Indicates the general visual or structural character of a skyline, such as its dominant form, density, or profile.
-
D.
hasDesignSignificance
Indicates that something possesses notable importance, impact, or relevance specifically in terms of its design.
-
E.
hasCallSignificance
Indicates that a particular call or communication event holds special importance, priority, or relevance within a given context or process.
- 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_69f34913d9048190befaa634025232be |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6be189f848190b9826b97b1191f26 |
completed | May 3, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6cef208190bc5cd43d96127004 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:48 a.m.