Triple
T7097333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Graham Coast |
E165364
|
entity |
| Predicate | hasTerrainCharacteristic |
P12436
|
FINISHED |
| Object | rugged |
—
|
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: rugged | Statement: [Graham Coast, hasTerrainCharacteristic, rugged]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTerrainCharacteristic Context triple: [Graham Coast, hasTerrainCharacteristic, rugged]
-
A.
terrainFeature
Indicates a relationship where one entity is a natural or constructed landform or surface characteristic associated with a given location or area.
-
B.
hasRockyTerrain
Indicates that the subject possesses or is characterized by rough, uneven, or rock-covered ground or surface conditions.
-
C.
hasAdvancedTerrain
Indicates that an entity possesses or is associated with terrain featuring complex, challenging, or enhanced physical characteristics beyond standard ground conditions.
-
D.
hasGeographyCharacteristic
chosen
Indicates that an entity possesses a specific geographical feature, property, or attribute.
-
E.
hasMountainousTerrain
Indicates that a location or area possesses predominantly mountainous physical terrain or landscape features.
- 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_69c6887e8c10819091cee237560d32da |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e5561dd08190be6b784754a0c1bc |
completed | March 27, 2026, 8:15 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c313e481908b61a23fc89f9332 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:41 p.m.