Triple
T9623767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Handley Page Victor |
E232406
|
entity |
| Predicate | enteredRAFServiceAsBomber |
P21857
|
FINISHED |
| Object | late 1950s |
—
|
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: late 1950s | Statement: [Handley Page Victor, enteredRAFServiceAsBomber, late 1950s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enteredRAFServiceAsBomber Context triple: [Handley Page Victor, enteredRAFServiceAsBomber, late 1950s]
-
A.
commanderOfRAF
Indicates that one entity serves as the commander or head of the Royal Air Force in relation to another entity.
-
B.
enteredRAFService
chosen
Indicates that an entity began service in the Royal Air Force (RAF).
-
C.
enteredUSAAFService
Indicates that an entity began active service in the United States Army Air Forces.
-
D.
periodOfRAFService
Indicates the time span during which an entity served in the Royal Air Force (RAF).
-
E.
knownInBritishServiceAs
Indicates that an entity is referred to or recognized by a particular name or designation specifically within the context of British service.
- 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_69ca848793ec8190a93a12383a754dc0 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9ad650a4819096258665bc3f410b |
completed | April 1, 2026, 10:23 p.m. |
| PD | Predicate disambiguation | batch_69ccd5aa1d2c8190a287bf1cf4a3037e |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:10 p.m.