Triple
T35016041
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nightosphere |
E1010054
|
entity |
| Predicate | transportTypeInside |
P195138
|
FINISHED |
| Object | floating platforms |
—
|
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: floating platforms | Statement: [Nightosphere, transportTypeInside, floating platforms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transportTypeInside Context triple: [Nightosphere, transportTypeInside, floating platforms]
-
A.
transportType
Indicates the mode or means of transportation used in carrying something or someone from one place to another.
-
B.
transportAccessType
Indicates the type or mode of transportation access available or used in a given context.
-
C.
transportSubmode
chosen
Indicates a more specific categorization of a general transport mode, defining the particular sub-type or variant of transportation being used.
-
D.
transportAssumption
Indicates an assumption that something can be transported or carried from one place or context to another.
-
E.
transportAccessBy
Indicates that one entity has access to or is served by a particular mode or means of transportation provided or enabled by another entity.
- 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_69f76dcc3ac8819096a3ed52f5fa2523 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff409ff5548190849c2d50e99bd807 |
completed | May 9, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69ff401a5e188190a72f945e910b4a6c |
completed | May 9, 2026, 2:09 p.m. |
Created at: May 3, 2026, 4:01 p.m.