Triple
T26694326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | western gull |
E672975
|
entity |
| Predicate | rangeExtendsTo |
P1673
|
FINISHED |
| Object | Baja California |
—
|
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: Baja California | Statement: [western gull, rangeExtendsTo, Baja California]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rangeExtendsTo Context triple: [western gull, rangeExtendsTo, Baja California]
-
A.
rangeExtendsFrom
Indicates that the spatial or conceptual extent of something begins at a specified point or boundary and continues outward from there.
-
B.
rangeIncludes
Indicates that the values or results associated with a property are expected to be of the specified type or types.
-
C.
rangeExpansion
Indicates an increase in the spatial or contextual extent over which something applies, operates, or is distributed.
-
D.
extendsTo
chosen
Indicates that one entity reaches, stretches, or continues its scope, influence, or coverage up to or into another entity.
-
E.
rangeExtenderOption
Indicates that an entity offers or is associated with an optional feature or configuration that extends its operational range.
- 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_69eecda2066c8190a344218afa5e89c1 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f61a17a7788190946f7e32d63cd43f |
completed | May 2, 2026, 3:36 p.m. |
| PD | Predicate disambiguation | batch_69f611ab768c8190b1849c15a3e59dda |
completed | May 2, 2026, 3 p.m. |
Created at: April 27, 2026, 3:27 a.m.