Triple
T16311731
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amazon Spheres |
E396071
|
entity |
| Predicate | Understory |
P83412
|
FINISHED |
| Object | immersive exhibit space |
—
|
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: immersive exhibit space | Statement: [Amazon Spheres, Understory, immersive exhibit space]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Understory Context triple: [Amazon Spheres, Understory, immersive exhibit space]
-
A.
hasUnderstory
chosen
Indicates that one entity possesses or includes an understory layer beneath a main canopy or upper layer within it.
-
B.
Höhepunkt
Indicates the climax or peak point reached within an event, process, or development.
-
C.
Waterline
Indicates the level or line on an object or surface that marks where water reaches or has reached.
-
D.
جایگاه
Indicates a positional or hierarchical relationship specifying the place, rank, or status of one entity relative to others.
-
E.
التيجان والأوسمة
Indicates the relationship of conferring, wearing, or possessing crowns and decorations (such as medals or orders of honor) as marks of rank, distinction, or recognition.
- 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_69d87f23bb088190a16fbb91a1957ea5 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e288dafb608190be35bd60342bb44e |
completed | April 17, 2026, 7:24 p.m. |
| PD | Predicate disambiguation | batch_69e219fa5508819097e9d383348bf174 |
completed | April 17, 2026, 11:31 a.m. |
Created at: April 10, 2026, 5:06 a.m.