Triple
T26694325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | western gull |
E672975
|
entity |
| Predicate | rangeExtendsFrom |
P161126
|
FINISHED |
| Object | British Columbia |
—
|
NE NERFINISHED |
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: British Columbia | Statement: [western gull, rangeExtendsFrom, British Columbia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rangeExtendsFrom Context triple: [western gull, rangeExtendsFrom, British Columbia]
-
A.
rangeExpansion
Indicates an increase in the spatial or contextual extent over which something applies, operates, or is distributed.
-
B.
rangeExtenderOption
Indicates that an entity offers or is associated with an optional feature or configuration that extends its operational range.
-
C.
rangeIncludes
Indicates that the values or results associated with a property are expected to be of the specified type or types.
-
D.
rangeVariant
Indicates that one entity is a variant or alternative form within the value range defined or covered by another entity.
-
E.
extendedFrom
Indicates that one entity is derived by adding to or building upon the scope, content, or structure of another entity.
- F. None of above. chosen
Provenance (4 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_69eecda2066c8190a344218afa5e89c1 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f6177ab31c8190ad205a5fed1ec9d8 |
completed | May 2, 2026, 3:25 p.m. |
| PD | Predicate disambiguation | batch_69f60b8bb0d08190ab5a9a2a8847c6f4 |
completed | May 2, 2026, 2:34 p.m. |
| PDg | Predicate description generation | batch_69f60f24ed608190bffe6c6084fc2f7a |
completed | May 2, 2026, 2:50 p.m. |
Created at: April 27, 2026, 3:27 a.m.