Triple
T37582274
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ceaulin |
E935003
|
entity |
| Predicate | authorityOnSubject |
P197042
|
FINISHED |
| Object | Bede |
—
|
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: Bede | Statement: [Ceaulin, authorityOnSubject, Bede]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: authorityOnSubject Context triple: [Ceaulin, authorityOnSubject, Bede]
-
A.
authorityBasedOn
Indicates that one entity’s authority or power is derived from, justified by, or contingent upon another specified basis or source.
-
B.
authorityGranted
Indicates that one entity has formally given another entity the power, rights, or permission to act or make decisions, typically within a defined scope or context.
-
C.
authorityWithin
Indicates that one entity holds recognized power, control, or decision-making authority inside the scope, domain, or jurisdiction defined by another entity.
-
D.
hasAuthorityOf
Indicates that one entity possesses and can exercise the official power, rights, or control that properly belong to another entity.
-
E.
authorityAffirmedBy
Indicates that the legitimacy or validity of an authority is confirmed, endorsed, or supported by another party or source.
- 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_69f76ece61dc8190a0ab33f8d87d0a7e |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fe744faca881908e11e90e0a35653f |
completed | May 8, 2026, 11:39 p.m. |
| PD | Predicate disambiguation | batch_69fe734cbf7081909a552c5cf3b5ea59 |
completed | May 8, 2026, 11:35 p.m. |
| PDg | Predicate description generation | batch_69fe744e9ee081909b362fc8609bc744 |
completed | May 8, 2026, 11:39 p.m. |
Created at: May 3, 2026, 4:17 p.m.