Triple
T34723686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alnôbak |
E1000988
|
entity |
| Predicate | subregionToday |
P9956
|
FINISHED |
| Object | New England states |
—
|
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: New England states | Statement: [Alnôbak, subregionToday, New England states]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subregionToday Context triple: [Alnôbak, subregionToday, New England states]
-
A.
subregionName
Indicates that one region is identified by a specific name used for a smaller or subordinate geographic or administrative area within a larger region.
-
B.
administrativeDivisionToday
Indicates that one entity currently functions as an administrative subdivision or jurisdictional unit within the other.
-
C.
regionSub
Indicates that one region is a subregion or contained part of another, larger region.
-
D.
subregionType
Indicates that one region is classified as a specific type or category of subregion within a larger geographic or administrative area.
-
E.
subregionOf
chosen
Indicates that one region is geographically or administratively contained within, and is a part of, another larger region.
- 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_69f76daeb6e48190a4c9a6b0edc80f72 |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f77ffa6b68819090257fed3802c239 |
completed | May 3, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69f7795978c481909e152cd1bd02dd07 |
completed | May 3, 2026, 4:35 p.m. |
Created at: May 3, 2026, 3:59 p.m.