Triple
T36420466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Victoria Cross to Guy Gibson |
E897138
|
entity |
| Predicate | serviceOfRecipient |
P18496
|
FINISHED |
| Object | Royal Air Force Bomber Command |
—
|
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: Royal Air Force Bomber Command | Statement: [Victoria Cross to Guy Gibson, serviceOfRecipient, Royal Air Force Bomber Command]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceOfRecipient Context triple: [Victoria Cross to Guy Gibson, serviceOfRecipient, Royal Air Force Bomber Command]
-
A.
serviceOf
Indicates that one entity performs, provides, or fulfills a function or duty on behalf of another entity.
-
B.
serviceFor
Indicates that one entity provides a service or performs functions on behalf of another entity.
-
C.
serviceFrom
Indicates that a service or transportation route originates from a specified source location or provider.
-
D.
serviceWith
Indicates that one entity provides or is associated with a particular service offered to or used by another entity.
-
E.
serviceIn
chosen
Indicates that one entity serves, operates, or performs its function within the context, scope, or domain of another entity.
- 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_69f76e559b10819099d6655a6e14587c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd6a1c1c4881908090053bc359b181 |
completed | May 8, 2026, 4:44 a.m. |
| PD | Predicate disambiguation | batch_69fd696f24d8819091033afacbdaadc5 |
completed | May 8, 2026, 4:41 a.m. |
Created at: May 3, 2026, 4:10 p.m.