Triple
T35422135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Forest Secret Area |
E1023822
|
entity |
| Predicate | mapIconShape |
P33696
|
FINISHED |
| Object | level tile on Forest of Illusion map |
—
|
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: level tile on Forest of Illusion map | Statement: [Forest Secret Area, mapIconShape, level tile on Forest of Illusion map]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mapIconShape Context triple: [Forest Secret Area, mapIconShape, level tile on Forest of Illusion map]
-
A.
iconShape
chosen
Indicates the geometric form or outline that an icon visually takes.
-
B.
mapSymbol
Indicates a correspondence where one symbol is used to represent, stand for, or denote another element within a mapping or representation system.
-
C.
mapShape
Indicates a correspondence between an original shape and its transformed or represented version in another space, system, or context.
-
D.
mapSymbolStandard
Indicates that a map symbol conforms to, or is defined according to, a particular cartographic standard or specification.
-
E.
typicalMapShape
Indicates that something has the usual or characteristic geometric form commonly associated with a map.
- 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_69f7958d59388190a937ac6f4c81d3c9 |
completed | May 3, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f7910770108190bdd39ddb5d304f54 |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4:03 p.m.