Triple
T18038376
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Service in the United Kingdom |
E431573
|
entity |
| Predicate | followedByReserveObligation |
P8511
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [National Service in the United Kingdom, followedByReserveObligation, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followedByReserveObligation Context triple: [National Service in the United Kingdom, followedByReserveObligation, yes]
-
A.
followedByResolution
Indicates that one event, state, or action is directly succeeded by a resolving event, state, or action in a sequence.
-
B.
obligationCondition
chosen
Indicates that one situation or state serves as the condition under which an obligation for an entity becomes active or must be fulfilled.
-
C.
hasOngoingObligations
Indicates that an entity is currently bound by duties or responsibilities that are still in effect and not yet fulfilled or terminated.
-
D.
mayBeFollowedBy
Indicates that one event, state, or item is allowed or able to occur immediately after another in a sequence.
-
E.
followedByInProtocol
Indicates that one step, action, or event in a protocol occurs immediately after another as the next prescribed step.
- 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_69d8b9050fb48190890155145deb0a66 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4be3cbe8c8190ba216eeebfc3cbec |
completed | April 19, 2026, 11:36 a.m. |
| PD | Predicate disambiguation | batch_69e3f908da508190a088aa837ea5b7af |
completed | April 18, 2026, 9:35 p.m. |
Created at: April 10, 2026, 10:25 a.m.