Triple
T32877032
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | kal-if-fee |
E840955
|
entity |
| Predicate | presidingExample |
P177803
|
FINISHED |
| Object | T'Pau |
—
|
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: T'Pau | Statement: [kal-if-fee, presidingExample, T'Pau]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: presidingExample Context triple: [kal-if-fee, presidingExample, T'Pau]
-
A.
presidingRole
Indicates that one entity holds an official position of authority or leadership over a proceeding, organization, or event involving another entity.
-
B.
trialPresidedOver
Indicates that a particular judge or authority figure oversaw and directed the proceedings of a specific trial.
-
C.
presidedAt
Indicates that one entity held a position of authority or leadership over the proceedings or activities that took place at a specific event or location.
-
D.
chiefJusticePresiding
Indicates that a specified chief justice is the one formally presiding over a particular court session, case, or judicial proceeding.
-
E.
alsoPresidedBy
Indicates that an event, organization, or proceeding is jointly overseen or led by an additional presiding entity alongside the primary one.
- 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_69f349436ee88190b72ee12d0f3f508e |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7051ad6e4819095e82bbd64761803 |
completed | May 3, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69f700fe24e08190998e2c96fbaaad38 |
completed | May 3, 2026, 8:02 a.m. |
| PDg | Predicate description generation | batch_69f70519f114819080659840c04d7911 |
completed | May 3, 2026, 8:19 a.m. |
Created at: May 1, 2026, 1:18 a.m.