Triple
T17560957
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GeoJSON |
E427694
|
entity |
| Predicate | topLevelMember |
P127959
|
FINISHED |
| Object | type |
—
|
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: type | Statement: [GeoJSON, topLevelMember, type]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: topLevelMember Context triple: [GeoJSON, topLevelMember, type]
-
A.
topLevel
Indicates that an entity occupies the highest or outermost level in a hierarchy, structure, or organizational arrangement, with no parent above it.
-
B.
topLevelRepresents
Indicates that one entity serves as the primary or overarching representation of another entity or concept at the highest level of abstraction or organization.
-
C.
topLevelOf
Indicates that one entity is the highest or most overarching level within the structure or hierarchy of another entity.
-
D.
topLevelHierarchy
Indicates that an entity occupies the highest position or root level within a hierarchical structure, with no parent above it.
-
E.
hasTopLevel
Indicates that one entity is the highest or primary element within a hierarchy or structure relative to another entity.
- 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_69d889e0385081908a04b66f4dd4bd0d |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e456267e208190a1238fbe1a535bb0 |
completed | April 19, 2026, 4:12 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fb39948190a82a597c5bac5c57 |
completed | April 18, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69e3bbb50b448190a59dd4be33c76db7 |
completed | April 18, 2026, 5:13 p.m. |
Created at: April 10, 2026, 5:50 a.m.