Triple
T2201137
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interior Lowlands |
E50491
|
entity |
| Predicate | relativeRelief |
P19604
|
FINISHED |
| Object | low to moderate |
—
|
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: low to moderate | Statement: [Interior Lowlands, relativeRelief, low to moderate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativeRelief Context triple: [Interior Lowlands, relativeRelief, low to moderate]
-
A.
hasRelativeRelief
chosen
Indicates a relationship where one entity is characterized by the degree of variation in elevation or relief relative to another reference entity or area.
-
B.
relativeLevel
Indicates a comparative relationship specifying how one entity’s level, degree, or intensity of some property stands relative to that of another entity.
-
C.
elevation
Indicates the vertical height or altitude of one entity relative to a reference level or another entity.
-
D.
relativeComfort
Indicates a comparative relationship where one entity is judged to be more or less comfortable than another under given conditions.
-
E.
relativePosition
Indicates the spatial relationship of one entity’s location with respect to another entity’s position.
- 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_69a88b044ab48190add007487680f009 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abbfa1b41c8190b0f7467d0dcdfbcd |
completed | March 7, 2026, 6:03 a.m. |
| PD | Predicate disambiguation | batch_69abbda706f4819094de73e1d1d1f539 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:46 p.m.