Triple
T20108734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Labrador (historical boundaries) |
E490268
|
entity |
| Predicate | boundaryStatus |
P138718
|
FINISHED |
| Object | historical |
—
|
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: historical | Statement: [Labrador (historical boundaries), boundaryStatus, historical]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: boundaryStatus Context triple: [Labrador (historical boundaries), boundaryStatus, historical]
-
A.
boundaryBetween
Indicates that something serves as a dividing line or limit separating two distinct regions, areas, or entities.
-
B.
boundaryReviewRegion
Indicates that a specified region is under consideration or subject to evaluation in a boundary review process.
-
C.
borderStateOf
Indicates that one state shares a common boundary or border with another state.
-
D.
boundaryName
Indicates the designated name or label assigned to a specific boundary or border between entities.
-
E.
boundaryCondition
Indicates the specific constraints or values imposed at the limits or edges of a system, domain, or process that govern its behavior there.
- 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_69da62636cc08190982cc71733a17b8d |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e666df1b148190a28ead2f7cce7aab |
completed | April 20, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69e54cf788188190a46cc49c9ce7617f |
completed | April 19, 2026, 9:45 p.m. |
| PDg | Predicate description generation | batch_69e54fc2bc3c819088c33cd263303433 |
completed | April 19, 2026, 9:57 p.m. |
Created at: April 11, 2026, 11:28 p.m.