Triple
T27682555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lloydminster |
E697944
|
entity |
| Predicate | borderMarker |
P49185
|
FINISHED |
| Object | Fourth Meridian |
—
|
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: Fourth Meridian | Statement: [Lloydminster, borderMarker, Fourth Meridian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderMarker Context triple: [Lloydminster, borderMarker, Fourth Meridian]
-
A.
borderPoint
Indicates a point that lies on the boundary between two regions or entities.
-
B.
marksBoundaryIn
chosen
Indicates that one entity serves as a boundary or delimiter within, or for a specific region or structure of, another entity.
-
C.
borderWithin
Indicates that one region’s border lies entirely inside the boundary of another region.
-
D.
borderDefinedBetween
Indicates that a boundary line or border is formally established between two geographic or political entities.
-
E.
borderCharacteristic
Indicates that one entity specifies a property, feature, or quality of the border or boundary of another entity.
- 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_69ef590df8708190af5488f0638e790c |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69fcf825ca7081909d06b0df33eb33f9 |
completed | May 7, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fcf42160f0819096812a8bf590875e |
completed | May 7, 2026, 8:20 p.m. |
Created at: April 27, 2026, 2:47 p.m.