Triple
T34753255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brian Falsworth |
E1001842
|
entity |
| Predicate | successorAsUnionJack |
P201426
|
FINISHED |
| Object | Joseph Chapman |
—
|
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: Joseph Chapman | Statement: [Brian Falsworth, successorAsUnionJack, Joseph Chapman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorAsUnionJack Context triple: [Brian Falsworth, successorAsUnionJack, Joseph Chapman]
-
A.
predecessorAsUnionJack
Indicates that one entity served as the immediate prior version or design of the Union Jack in relation to another entity.
-
B.
successorInUK
Indicates that one entity directly follows another in a succession specific to the United Kingdom, such as in an official role, title, or office.
-
C.
featuredUnionJackVariant
Indicates that an entity prominently displays or uses a specific variant of the Union Jack as a key identifying or decorative feature.
-
D.
successorInWales
Indicates that one entity is the successor of another in a specific role, position, or function within Wales.
-
E.
successorInScotland
Indicates that one entity is the next holder of a role, title, or position in Scotland following another entity.
- 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_69f76db0fb30819096709d43f9a1f45f |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fff4530f908190afe9387f732c2b7e |
completed | May 10, 2026, 2:58 a.m. |
| PD | Predicate disambiguation | batch_69fff3c01a64819091196875b0c88607 |
completed | May 10, 2026, 2:56 a.m. |
| PDg | Predicate description generation | batch_69fff4525ce48190b1d760539e68aadc |
completed | May 10, 2026, 2:58 a.m. |
Created at: May 3, 2026, 3:59 p.m.