Triple
T6373935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wonderland station |
E143415
|
entity |
| Predicate | hasAdjacentEnvironment |
P13155
|
FINISHED |
| Object | coastal area |
—
|
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: coastal area | Statement: [Wonderland station, hasAdjacentEnvironment, coastal area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAdjacentEnvironment Context triple: [Wonderland station, hasAdjacentEnvironment, coastal area]
-
A.
isAdjacentTo
Indicates that one entity is directly next to or bordering another without anything of the same type in between.
-
B.
hasAdjacentUse
Indicates that one entity is used or occurs directly next to another in space, time, or sequence.
-
C.
isEnvironmentOf
Indicates that one entity serves as the surrounding conditions, context, or setting in which another entity exists, operates, or occurs.
-
D.
hasSurroundings
chosen
Indicates that an entity is located within or encircled by a particular environment, context, or set of surrounding elements.
-
E.
hasAdjacentSettlement
Indicates that one settlement is located directly next to or bordering another settlement.
- 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_69c008d9f4348190ab598a2913259a1c |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c068390af08190967a3d25ec9a50e5 |
completed | March 22, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69c060ee055081908c79a1d151bd74cd |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:33 p.m.