Triple
T37665786
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metro Kingdom |
E937816
|
entity |
| Predicate | hasPlatformingStyle |
P196769
|
FINISHED |
| Object | building-to-building jumps |
—
|
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: building-to-building jumps | Statement: [Metro Kingdom, hasPlatformingStyle, building-to-building jumps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlatformingStyle Context triple: [Metro Kingdom, hasPlatformingStyle, building-to-building jumps]
-
A.
hasSidePlatforms
Indicates that something is equipped with platforms located on its sides, typically for access, support, or operation.
-
B.
hasPlatformOn
Indicates that one entity is physically supported by or situated on the surface or structure of another entity.
-
C.
hasPlatformEdge
Indicates that an entity possesses or includes a boundary or edge associated with a platform.
-
D.
hasPlatformType
Indicates that an entity is associated with or characterized by a specific type or category of platform.
-
E.
hasDeepPlatform
Indicates that one entity possesses or provides a platform characterized by significant depth, capability, or extensiveness in supporting another entity’s activities or functions.
- 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fe6739d4dc8190ae7505c089bbac29 |
completed | May 8, 2026, 10:44 p.m. |
| PD | Predicate disambiguation | batch_69fe6541dffc81909c66a61ba69f38fc |
completed | May 8, 2026, 10:35 p.m. |
| PDg | Predicate description generation | batch_69fe673905408190a2ae68c2c9563403 |
completed | May 8, 2026, 10:44 p.m. |
Created at: May 3, 2026, 4:18 p.m.