Triple
T8219679
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mountain City |
E192025
|
entity |
| Predicate | associatedWithTerrain |
P5378
|
FINISHED |
| Object | mountainous terrain |
—
|
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: mountainous terrain | Statement: [Mountain City, associatedWithTerrain, mountainous terrain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithTerrain Context triple: [Mountain City, associatedWithTerrain, mountainous terrain]
-
A.
locatedOnTerrain
Indicates that one entity is physically situated on or atop a particular terrain surface.
-
B.
terrainIncludes
Indicates that a specified terrain area contains or encompasses another geographic or environmental feature within its boundaries.
-
C.
hasRockyTerrain
Indicates that the subject possesses or is characterized by rough, uneven, or rock-covered ground or surface conditions.
-
D.
usesGroundSystem
Indicates that one entity operates, relies on, or interacts with a particular ground-based system to perform its functions or services.
-
E.
terrainFeature
chosen
Indicates a relationship where one entity is a natural or constructed landform or surface characteristic associated with a given location or area.
- 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_69ca82c9a8ac81908b011c38698456e4 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb7772b76c8190b1952650c736eb91 |
completed | March 31, 2026, 7:27 a.m. |
| PD | Predicate disambiguation | batch_69cb36af41e081909dee92b9bc4947f1 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:45 p.m.