Triple
T31744378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | V-bomber force |
E810228
|
entity |
| Predicate | VictorLaterUse |
P6937
|
FINISHED |
| Object | aerial refuelling tanker |
—
|
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: aerial refuelling tanker | Statement: [V-bomber force, VictorLaterUse, aerial refuelling tanker]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: VictorLaterUse Context triple: [V-bomber force, VictorLaterUse, aerial refuelling tanker]
-
A.
victor
Indicates that one entity is the winner or has prevailed over another in a contest, conflict, or competition.
-
B.
VictorRole
Indicates that an entity holds the role or status of a victor (winner) in a competitive or conflict-based context relative to another entity or event.
-
C.
isCoVictorWith
Indicates that two or more entities share victory together in the same event, competition, or achievement.
-
D.
laterUsedBy
chosen
Indicates that something is subsequently utilized or employed by a specified entity at a later time.
-
E.
rulingMonarchOfVictor
Indicates that one entity is the reigning monarch who achieved victory over another entity, typically in a conflict or competition.
- 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_69f348e233cc819083b6695f70cd75d8 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca3dedc81908b519d53d2909868 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 30, 2026, 11:26 p.m.