Triple
T13219412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sky Land |
E314709
|
entity |
| Predicate | hasMapStructure |
P108574
|
FINISHED |
| Object | ground section |
—
|
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: ground section | Statement: [Sky Land, hasMapStructure, ground section]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMapStructure Context triple: [Sky Land, hasMapStructure, ground section]
-
A.
hasMapType
Indicates that one entity is associated with a specific type or category of map.
-
B.
hasMapReference
Indicates that an entity is associated with a specific map or map location reference.
-
C.
hasKeyStructure
Indicates that one entity possesses or defines the primary structural framework or core structural pattern of another entity.
-
D.
hasMapBy
Indicates that one entity is represented, depicted, or detailed by a specific map associated with it.
-
E.
hasMapState
Indicates that an entity is associated with a particular state or condition of a map (such as its configuration, status, or version).
- 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_69d806affc688190a25b6ccc588e9c72 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf581508190883033f0c961736a |
completed | April 10, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69d98bc938f081909f123bdf1263ff7f |
completed | April 10, 2026, 11:46 p.m. |
| PDg | Predicate description generation | batch_69d98c959ba08190adf29dc0c4e1fca6 |
completed | April 10, 2026, 11:49 p.m. |
Created at: April 9, 2026, 9:18 p.m.