Triple
T37661587
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | End Barrens |
E937728
|
entity |
| Predicate | hasSurfaceBlock |
P202162
|
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: [End Barrens, hasSurfaceBlock, end stone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSurfaceBlock Context triple: [End Barrens, hasSurfaceBlock, end stone]
-
A.
hasSurfaceLevel
Indicates that one entity possesses or is characterized by a particular degree or measure of surface level (e.g., depth, detail, or superficiality).
-
B.
hasSurfaceSections
Indicates that an entity is composed of or divided into distinct sections or parts of its surface.
-
C.
hasSurfaceBody
Indicates that one entity possesses or is characterized by a particular surface or outer body.
-
D.
hasSurfaceFeatureState
Indicates that an entity currently exhibits a particular condition or status of one of its surface features.
-
E.
hasSurfaceBuilding
Indicates that one entity possesses or is associated with a building located on its surface.
- 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a005b2e0a9c819081c6f7ccbef49ff8 |
completed | May 10, 2026, 10:17 a.m. |
| PD | Predicate disambiguation | batch_6a005a8bcde88190ace2bc0215e26430 |
completed | May 10, 2026, 10:14 a.m. |
| PDg | Predicate description generation | batch_6a005b2cdbc881908b433623e3252df5 |
completed | May 10, 2026, 10:17 a.m. |
Created at: May 3, 2026, 4:18 p.m.