Triple
T31738528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iberian wolf |
E810069
|
entity |
| Predicate | mainRange |
P142593
|
FINISHED |
| Object | northwestern Iberian Peninsula |
—
|
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: northwestern Iberian Peninsula | Statement: [Iberian wolf, mainRange, northwestern Iberian Peninsula]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainRange Context triple: [Iberian wolf, mainRange, northwestern Iberian Peninsula]
-
A.
coreRange
chosen
Indicates the primary spatial or temporal extent within which an entity, phenomenon, or relationship is predominantly present or valid.
-
B.
rangeOf
Indicates that one entity specifies the set of possible values (range) that another entity’s outputs or properties can take.
-
C.
majorRangeIncludes
Indicates that a major range (such as a primary geographic or categorical span) encompasses or contains another specified range.
-
D.
designedRange
Indicates the intended or specified range within which something is designed to operate or be effective.
-
E.
testRange
Indicates that a value, condition, or behavior is being evaluated to determine whether it falls within a specified range or interval.
- 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_69f348e0e4908190a884582eca646fb7 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca3dedc81908b519d53d2909868 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 30, 2026, 11:24 p.m.