Triple
T15609674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jeddah Tower |
E375253
|
entity |
| Predicate | intendedRecord |
P88492
|
FINISHED |
| Object | tallest building in the world |
—
|
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: tallest building in the world | Statement: [Jeddah Tower, intendedRecord, tallest building in the world]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedRecord Context triple: [Jeddah Tower, intendedRecord, tallest building in the world]
-
A.
isRecord
Indicates that one entity functions as an official or authoritative record of another entity or of some information.
-
B.
intendedWith
Indicates that one entity is the planned or desired target, recipient, or context for the use or application of another entity.
-
C.
setRecordFor
Indicates establishing or updating a specific record associated with an entity or context.
-
D.
poweredRecord
Indicates that one entity functions as a powered or electrified version of another entity, typically enabling enhanced or active operation.
-
E.
intendsTo
chosen
Indicates that one entity has the purpose, plan, or desire to perform an action involving another entity or outcome.
- 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_69d85ccf2794819096cda4cbcb02d478 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04e8024948190a6c711f2e5c2aac4 |
completed | April 16, 2026, 2:50 a.m. |
| PD | Predicate disambiguation | batch_69deda844af081909e658ebc9d9b403d |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:13 a.m.