Triple
T37539517
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bronzebeard clan |
E933288
|
entity |
| Predicate | terrainPreference |
P130186
|
FINISHED |
| Object | mountainous regions |
—
|
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 regions | Statement: [Bronzebeard clan, terrainPreference, mountainous regions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terrainPreference Context triple: [Bronzebeard clan, terrainPreference, mountainous regions]
-
A.
terrainCapability
Indicates the types of terrain or ground conditions in which an entity can effectively operate or function.
-
B.
skiTerrainType
Indicates the type of terrain or surface on which the skiing activity takes place.
-
C.
elevationPreference
chosen
Indicates a tendency or preference for a certain elevation or altitude relative to other possible elevation levels.
-
D.
involvesTerrain
Indicates that the relationship or action takes place in, across, or is directly affected by a specified type of terrain or landform.
-
E.
terrainFeature
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_69f76ec999288190ae26ec7b6aea7046 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba5eec0448190a5e6f0c43fdcd0e3 |
completed | May 6, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69fba34edd548190bfa980e6e16e0a88 |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.