Triple
T26213104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wellington Mk IC |
E655541
|
entity |
| Predicate | enteredBomberCommandService |
P2339
|
FINISHED |
| Object | early phase of World War II |
—
|
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: early phase of World War II | Statement: [Wellington Mk IC, enteredBomberCommandService, early phase of World War II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enteredBomberCommandService Context triple: [Wellington Mk IC, enteredBomberCommandService, early phase of World War II]
-
A.
hasBomber
Indicates that an entity possesses, controls, or is associated with a bomber aircraft.
-
B.
compatibleBomber
Indicates that one entity can function effectively as a bomber in conjunction with, or as a suitable counterpart to, another specified entity.
-
C.
commanderOnBoard
Indicates that a specific individual holds the role of commanding officer on a particular vehicle, vessel, or craft during its operation.
-
D.
enteredService
chosen
Indicates that an entity began active use or operation at a specific time or in a specific context.
-
E.
enteredJMSDFService
Indicates that an entity began active service in the Japan Maritime Self-Defense Force (JMSDF).
- 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_69ee5b49adb4819086545280d4ef6337 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f60d190d048190ac0338b37443ab59 |
completed | May 2, 2026, 2:41 p.m. |
| PD | Predicate disambiguation | batch_69f602d2ec748190ae95154f34c7878f |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 26, 2026, 8:53 p.m.