Triple
T36420474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Victoria Cross to Guy Gibson |
E897138
|
entity |
| Predicate | serviceRoleOfRecipient |
P37410
|
FINISHED |
| Object | bomber pilot |
—
|
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: bomber pilot | Statement: [Victoria Cross to Guy Gibson, serviceRoleOfRecipient, bomber pilot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceRoleOfRecipient Context triple: [Victoria Cross to Guy Gibson, serviceRoleOfRecipient, bomber pilot]
-
A.
serviceEntryRole
Indicates the role or function an entity performs in the context of providing or managing a particular service.
-
B.
serviceAreaRole
Indicates the specific function or responsibility an entity has within a defined service area.
-
C.
serviceFor
Indicates that one entity provides a service or performs functions on behalf of another entity.
-
D.
servesRole
Indicates that one entity performs, fulfills, or occupies a particular function, position, or responsibility in relation to another entity.
-
E.
beneficiaryRole
chosen
Indicates that one entity serves as the beneficiary or recipient of an action, service, or resource provided by 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_69fd6dbd1b648190b1a0b391c03aebc5 |
completed | May 8, 2026, 4:59 a.m. |
| PD | Predicate disambiguation | batch_69fd6a9020548190bbfa845360ac85fb |
completed | May 8, 2026, 4:46 a.m. |
Created at: May 3, 2026, 4:10 p.m.