Triple
T25176865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lieut-Bailiff (when acting) |
E630471
|
entity |
| Predicate | actsWhen |
P12708
|
FINISHED |
| Object | Bailiff of Jersey is absent |
—
|
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: Bailiff of Jersey is absent | Statement: [Lieut-Bailiff (when acting), actsWhen, Bailiff of Jersey is absent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: actsWhen Context triple: [Lieut-Bailiff (when acting), actsWhen, Bailiff of Jersey is absent]
-
A.
actsOn
Indicates that one entity performs an action that affects, targets, or is directed toward another entity.
-
B.
actsFor
Indicates that one entity performs actions or exercises authority on behalf of another entity.
-
C.
occursWhen
chosen
Indicates that one event or condition happens at the same time or is triggered under the circumstances defined by another event or condition.
-
D.
actAs
Indicates that one entity performs the function, role, or behavior of another entity, effectively serving or operating in its place.
-
E.
actuatedBy
Indicates that an action, process, or mechanism is initiated, driven, or controlled by a specific agent or cause.
- 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_69e75a88fdf081908e47ae6e195c14e1 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f46dc040088190958bb7a6633fd016 |
completed | May 1, 2026, 9:09 a.m. |
| PD | Predicate disambiguation | batch_69f45cfb53f4819099bba48c5057e787 |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 21, 2026, 12:34 p.m.