Triple
T3962329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wallace Line |
E85932
|
entity |
| Predicate | notExactPoliticalBoundary |
P53620
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Wallace Line, notExactPoliticalBoundary, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notExactPoliticalBoundary Context triple: [Wallace Line, notExactPoliticalBoundary, true]
-
A.
isPoliticalBoundary
Indicates that one entity serves as a dividing line or border that separates distinct political or administrative jurisdictions.
-
B.
nearInternationalBoundary
Indicates that one entity is located close to an international boundary separating two or more countries.
-
C.
provinceBordering
Indicates that two provinces share a common boundary or border with each other.
-
D.
borderedPoliticalSpheres
Indicates that two political regions or jurisdictions share a common boundary.
-
E.
borderRegion
Indicates a region that lies along or near the boundary separating two distinct geographic or political areas.
- 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_69aed93a96908190bcbdbfa718f155bd |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefba878a48190a2e234d775215938 |
completed | March 9, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69aef8efcf3c81908ccf61d9ce26b0c0 |
completed | March 9, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69aefba6b9848190a7b0fb66100a2a0c |
completed | March 9, 2026, 4:56 p.m. |
Created at: March 9, 2026, 3:31 p.m.