Triple
T31953337
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Team Captain America |
E815839
|
entity |
| Predicate | primaryLocationOfBattle |
P12233
|
FINISHED |
| Object | Leipzig/Halle Airport |
E200407
|
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: Leipzig/Halle Airport | Statement: [Team Captain America, primaryLocationOfBattle, Leipzig/Halle Airport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryLocationOfBattle Context triple: [Team Captain America, primaryLocationOfBattle, Leipzig/Halle Airport]
-
A.
placeOfMainEngagement
Indicates the primary location where an entity carries out its main activities, operations, or engagements.
-
B.
battleOccurredOn
chosen
Indicates that a specific battle took place at or on a particular location or date.
-
C.
battleOccurredNear
Indicates that a battle took place in spatial proximity to a specified location or entity.
-
D.
primaryBattlefieldOf
Indicates that a specified location serves as the main or most significant battlefield where a particular conflict or war primarily took place.
-
E.
battleFoughtBy
Indicates that a specific battle was fought by a particular participant or group of participants.
- 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_69f348f4ec708190abbb2a7c3ed58844 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2e8a4dbae0819085aaca09c5386f58 |
completed | June 14, 2026, 11:02 a.m. |
| PD | Predicate disambiguation | batch_6a0379eaa540819095a1c5d9f3513f9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:08 a.m.