Triple
T32053020
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mermaid Lagoon |
E818539
|
entity |
| Predicate | indoorSectionName |
P173157
|
FINISHED |
| Object | Triton’s Kingdom |
—
|
NE NERFINISHED |
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: Triton’s Kingdom | Statement: [Mermaid Lagoon, indoorSectionName, Triton’s Kingdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: indoorSectionName Context triple: [Mermaid Lagoon, indoorSectionName, Triton’s Kingdom]
-
A.
indoorTitle
Indicates that an entity holds a title, role, or designation specifically applicable within an indoor context or indoor environment.
-
B.
indoorComponent
Indicates that one entity functions as an indoor part, element, or feature of another entity.
-
C.
indoorOrOutdoor
Indicates whether an activity, event, or entity occurs inside a building (indoors) or outside in open air (outdoors).
-
D.
hasIndoorType
Indicates that an entity is associated with a specific type or category of indoor environment or indoor feature.
-
E.
indoorAdvantage
Indicates that an entity has a beneficial edge or improved performance when conditions or activities occur indoors rather than outdoors.
- 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_69f348fdacec8190b9f74375ca3b2094 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b4ed587c8190868dba58046328c9 |
completed | May 3, 2026, 2:37 a.m. |
| PD | Predicate disambiguation | batch_69f6b154b3dc819087115f5f63f7b00f |
completed | May 3, 2026, 2:22 a.m. |
| PDg | Predicate description generation | batch_69f6b267b90c8190807208cadce5ae8d |
completed | May 3, 2026, 2:26 a.m. |
Created at: May 1, 2026, 12:20 a.m.