Triple
T31953371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle at Leipzig-Halle Airport |
E815840
|
entity |
| Predicate | leaderOfSideA |
P89460
|
FINISHED |
| Object | Tony Stark |
—
|
NE NERFINISHED |
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: Tony Stark | Statement: [Battle at Leipzig-Halle Airport, leaderOfSideA, Tony Stark]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leaderOfSideA Context triple: [Battle at Leipzig-Halle Airport, leaderOfSideA, Tony Stark]
-
A.
commandersSide1
chosen
Indicates that the referenced commander is aligned with or belongs to the first side/party in a conflict, competition, or opposing pair.
-
B.
notableLeaderSide
Indicates that a person is a prominent or distinguished leader associated with a particular side, faction, or party in a conflict or competition.
-
C.
commanderOfVictoriousSide
Indicates that one entity served as the commanding leader of the side that achieved victory in a conflict or competition relative to another entity.
-
D.
notableCommanderSide
Indicates that a particular military or strategic side is notably commanded or led by a specified commander.
-
E.
commandersSide
Indicates that one entity is on the same side, faction, or team as the commander in a conflict or competitive context.
- 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_69f348f4ec708190abbb2a7c3ed58844 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7431c0eec81909ead443e07d75e18 |
completed | May 3, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69f74143cf708190a12d487884298437 |
completed | May 3, 2026, 12:36 p.m. |
Created at: May 1, 2026, 12:08 a.m.