Triple
T8386103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Britannia Prima |
E197821
|
entity |
| Predicate | statusOfLocation |
P33417
|
FINISHED |
| Object | disputed among historians |
—
|
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: disputed among historians | Statement: [Britannia Prima, statusOfLocation, disputed among historians]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusOfLocation Context triple: [Britannia Prima, statusOfLocation, disputed among historians]
-
A.
locationStatus
Indicates the current state or condition of an entity with respect to a specific location (e.g., present, absent, en route, or unknown).
-
B.
localStatus
Indicates the current condition or state of an entity within a specific local context or environment.
-
C.
landerStatus
Indicates the current operational or situational state of a lander in its mission lifecycle.
-
D.
statusInRegion
chosen
Indicates the specific status or condition an entity holds within a particular geographic or administrative region.
-
E.
coordinateStatus
Indicates that one entity’s status is aligned, synchronized, or made consistent with another entity’s status or with a shared reference state.
- 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_69ca82f749388190bffbea6dfb509016 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb80e1bcdc81909111aa33ee996e0a |
completed | March 31, 2026, 8:08 a.m. |
| PD | Predicate disambiguation | batch_69cb70cfe82881909fe374ba52649e84 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 6:02 p.m.