Triple
T2227598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pocahontas |
E48687
|
entity |
| Predicate | laterLegalStatus |
P18056
|
FINISHED |
| Object | subject of the English Crown |
—
|
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: subject of the English Crown | Statement: [Pocahontas, laterLegalStatus, subject of the English Crown]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterLegalStatus Context triple: [Pocahontas, laterLegalStatus, subject of the English Crown]
-
A.
hasLegalStatus
Indicates that an entity possesses a particular legal classification, recognition, or standing under law.
-
B.
legalStatusClarifiedBy
Indicates that the legal status of something is defined, explained, or resolved by a specific document, decision, or authoritative act.
-
C.
laterStatus
Indicates that one entity represents a subsequent or resulting status or condition of another entity in time.
-
D.
laterLegalJurisdiction
chosen
Indicates that one legal jurisdiction succeeds or replaces another jurisdiction at a later point in time.
-
E.
legalStatusModern
Indicates the current legal standing or classification of an entity under contemporary law or regulatory frameworks.
- 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_69a88aa51b388190949868ec9766e587 |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc0670ce48190b98814064bff0517 |
completed | March 7, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69abbdadbb0c8190b3a1ede31b8acbfa |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:47 p.m.