Triple
T33775080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House Tarth |
E865493
|
entity |
| Predicate | terrainOfDomain |
P80940
|
FINISHED |
| Object | mountainous island |
—
|
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 island | Statement: [House Tarth, terrainOfDomain, mountainous island]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terrainOfDomain Context triple: [House Tarth, terrainOfDomain, mountainous island]
-
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.
terrainIncludes
Indicates that a specified terrain area contains or encompasses another geographic or environmental feature within its boundaries.
-
C.
topographicalCategory
chosen
Indicates the type of landform or surface feature that characterizes the physical terrain associated with an entity.
-
D.
topographyBasedOn
Indicates that the topographical characteristics of one entity are derived from, determined by, or modeled using the topography of another entity.
-
E.
landerType
Indicates the specific kind or category of lander involved in the relationship or action.
- 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_69f3498df6f88190bf9647ea4e4a956e |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc5740fc81909774a4f65201a3ff |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:45 a.m.