Triple
T37661533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Small End Islands |
E937727
|
entity |
| Predicate | terrainBlock |
P100822
|
FINISHED |
| Object | End Stone |
—
|
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: End Stone | Statement: [Small End Islands, terrainBlock, End Stone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terrainBlock Context triple: [Small End Islands, terrainBlock, End Stone]
-
A.
terrainIncludes
Indicates that a specified terrain area contains or encompasses another geographic or environmental feature within its boundaries.
-
B.
terrainFeature
Indicates a relationship where one entity is a natural or constructed landform or surface characteristic associated with a given location or area.
-
C.
terrainMaterial
chosen
Indicates the type of physical surface or ground substance that composes a given terrain.
-
D.
terrainSpecialization
Indicates a relationship where an entity is particularly adapted or optimized for operation, performance, or use within a specific type of terrain.
-
E.
terrainMode
Indicates that an entity operates or is configured in a specific terrain-related mode or setting.
- 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbaa1321b48190af92a3e7ec24ec5b |
completed | May 6, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69fba8860f98819080b7bab05837b974 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:18 p.m.