Triple
T8136321
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Trustees |
E189977
|
entity |
| Predicate | predecessorFunction |
P81677
|
FINISHED |
| Object | Civil List oversight arrangements |
—
|
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: Civil List oversight arrangements | Statement: [Royal Trustees, predecessorFunction, Civil List oversight arrangements]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predecessorFunction Context triple: [Royal Trustees, predecessorFunction, Civil List oversight arrangements]
-
A.
predecessor
Indicates that one entity comes before another in an ordered sequence or succession.
-
B.
predecessorOperator
Indicates that one operator precedes another in an ordered sequence or process.
-
C.
predecessorFamily
Indicates that one family is the earlier or ancestral family from which another family descends or follows.
-
D.
predecessorService
Indicates that one service must be completed or occur before another service can begin or be considered.
-
E.
predecessorName
Indicates that the value is the name of an entity that directly precedes another in an ordered sequence or lineage.
- 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_69ca82bd9900819099477cdc2eb4244f |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4c4c2e388190b86854f8b1765e61 |
completed | March 31, 2026, 4:23 a.m. |
| PD | Predicate disambiguation | batch_69cb3696379c8190a20965e59ed8f370 |
completed | March 31, 2026, 2:51 a.m. |
| PDg | Predicate description generation | batch_69cb4c496a8c81909aea840248d85d50 |
completed | March 31, 2026, 4:23 a.m. |
Created at: March 30, 2026, 5:35 p.m.