Triple
T36420463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Victoria Cross to Guy Gibson |
E897138
|
entity |
| Predicate | relatedUnitNickname |
P6622
|
FINISHED |
| Object | Dambusters |
E808265
|
NE 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: Dambusters | Statement: [Victoria Cross to Guy Gibson, relatedUnitNickname, Dambusters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedUnitNickname Context triple: [Victoria Cross to Guy Gibson, relatedUnitNickname, Dambusters]
-
A.
nicknameOfParentUnit
Indicates that one unit serves as an informal or alternative name (nickname) for its parent unit.
-
B.
nicknameOfUnitUsing
Indicates that one unit serves as an informal or alternative name (nickname) for another unit that is being used.
-
C.
notableTeamNickname
chosen
Indicates that a team is commonly known by a particular nickname that is notable or widely recognized.
-
D.
listedUnit
Indicates that an entity is specified or recorded as a particular unit in a list or catalog.
-
E.
relatedMilitaryUnit
Indicates that there is an association or connection between two military units, such as organizational, operational, or historical linkage.
- F. None of above.
Provenance (4 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_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a39c40c4c9c8190923dab70e38900b1 |
completed | June 22, 2026, 11:23 p.m. |
| PD | Predicate disambiguation | batch_6a037a0a54cc8190868c1bfa1590d1a6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:10 p.m.