Triple
T9882217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Big Wing controversy |
E180836
|
entity |
| Predicate | opposedTactic |
P437
|
FINISHED |
| Object | small fighter formation |
—
|
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: small fighter formation | Statement: [Big Wing controversy, opposedTactic, small fighter formation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opposedTactic Context triple: [Big Wing controversy, opposedTactic, small fighter formation]
-
A.
tactic
Indicates a strategic method or maneuver employed by one entity to influence, counter, or gain advantage over another in a specific context.
-
B.
opposedBy
chosen
Indicates that one entity actively resists, disagrees with, or works against the actions, views, or position of another entity.
-
C.
positionOpposed
Indicates that two entities hold positions or stances that are in direct conflict or opposition to each other.
-
D.
opposingForce
Indicates a relationship where one entity actively resists, counters, or works against the actions, goals, or influence of another entity.
-
E.
opposedOutcome
Indicates that one entity’s outcome is in conflict with, counters, or works against the outcome associated with another entity.
- 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_69ca828082cc8190a40f8d299caa6545 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cdb418417c8190b00dea8916a2e102 |
completed | April 2, 2026, 12:11 a.m. |
| PD | Predicate disambiguation | batch_69cd1d810ed48190a252b70e9390c8f3 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:38 p.m.