Triple
T27774128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Main Deck (Tokyo Tower) |
E699137
|
entity |
| Predicate | hasOutdoorElements |
P169949
|
FINISHED |
| Object | partially |
—
|
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: partially | Statement: [Main Deck (Tokyo Tower), hasOutdoorElements, partially]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOutdoorElements Context triple: [Main Deck (Tokyo Tower), hasOutdoorElements, partially]
-
A.
hasOutdoorType
Indicates that an entity is associated with a specific type or category of outdoor environment or feature.
-
B.
isOutdoor
Indicates that an entity or activity takes place outside, in an open-air or non-enclosed environment.
-
C.
hasOutdoorResource
Indicates that an entity is associated with, provides, or includes access to an outdoor resource or facility.
-
D.
hasOutdoorFocus
Indicates a relationship where an entity is primarily concerned with, oriented toward, or specialized in outdoor environments, activities, or contexts.
-
E.
hasOutdoorLocation
Indicates that an entity is associated with or possesses a specific outdoor place or setting.
- 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_69ef6a4b5a9081909c9111396c2be3d2 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f688d015908190ad5df37030ecf332 |
completed | May 2, 2026, 11:29 p.m. |
| PD | Predicate disambiguation | batch_69f68609c0b08190a8e1238a4d97c270 |
completed | May 2, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69f688034580819086a0f9100645f8ba |
completed | May 2, 2026, 11:25 p.m. |
Created at: April 27, 2026, 5:04 p.m.