Triple
T35421541
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Donut Secret 1 |
E1023807
|
entity |
| Predicate | overworldMapNodeShape |
P118334
|
FINISHED |
| Object | water level node |
—
|
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: water level node | Statement: [Donut Secret 1, overworldMapNodeShape, water level node]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: overworldMapNodeShape Context triple: [Donut Secret 1, overworldMapNodeShape, water level node]
-
A.
mapShape
Indicates a correspondence between an original shape and its transformed or represented version in another space, system, or context.
-
B.
typicalMapShape
Indicates that something has the usual or characteristic geometric form commonly associated with a map.
-
C.
hasWorldMapNodeType
chosen
Indicates that something is associated with a specific type or category of node within a world map structure.
-
D.
hasOverworldMapStyle
Indicates that an entity is associated with or uses a particular style or format for its overworld map.
-
E.
routeSymbolShape
Indicates the specific geometric form or outline used to depict a route’s symbol in a visual or cartographic representation.
- 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_69f76df6704081909900c60be10d5849 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79da9f80c8190b0afd8509f28747b |
completed | May 3, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69f79617d40481909ba372f94209c08b |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:03 p.m.