Triple
T1668942
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Power Map |
E36077
|
entity |
| Predicate | visualOutput |
P23550
|
FINISHED |
| Object | 3D map scenes |
—
|
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: 3D map scenes | Statement: [Power Map, visualOutput, 3D map scenes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: visualOutput Context triple: [Power Map, visualOutput, 3D map scenes]
-
A.
visualElements
Indicates that one entity contains, uses, or is characterized by specific visual components or graphical features associated with another entity.
-
B.
visualForm
Indicates the visual appearance, shape, or structural pattern that characterizes how something looks.
-
C.
visionOrSign
Indicates a relationship where something is perceived or presented as a vision, sign, or symbolic manifestation, often conveying a message, omen, or divine indication.
-
D.
visualizationLibrary
Indicates that an entity uses, depends on, or is implemented with a particular visualization library for rendering or displaying visual data.
-
E.
displays
chosen
Indicates that one entity visually presents or shows another entity’s content or information.
- 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_69a8861286808190939afff3ce8ee31e |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69abc0e8d5648190915ff689c7ca42bc |
completed | March 7, 2026, 6:08 a.m. |
| PD | Predicate disambiguation | batch_69a907d331748190963d4ab1a2741537 |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:29 p.m.