Triple
T20260182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Transall C-160 |
E498811
|
entity |
| Predicate | allianceProject |
P139433
|
FINISHED |
| Object | Franco-German military cooperation |
—
|
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: Franco-German military cooperation | Statement: [Transall C-160, allianceProject, Franco-German military cooperation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allianceProject Context triple: [Transall C-160, allianceProject, Franco-German military cooperation]
-
A.
alliance
Indicates a formal cooperative relationship between entities who agree to support each other in shared goals or interests.
-
B.
allianceUse
Indicates that one party makes use of, benefits from, or leverages an alliance or allied relationship with another party.
-
C.
allianceHubFor
Indicates that one entity serves as a central coordinating hub or focal point for an alliance involving another entity.
-
D.
allianceStructure
Indicates the organizational or relational configuration that defines how members of an alliance are structured and interconnected.
-
E.
allianceInteraction
Indicates an interaction or cooperative engagement occurring specifically between allied entities within an alliance.
- F. None of above. chosen
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_69da6275fa6c8190952924930adee150 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e674c90d00819082f68822635ee86a |
completed | April 20, 2026, 6:47 p.m. |
| PD | Predicate disambiguation | batch_69e55b1b23f88190bdcbe2f81dd226dd |
completed | April 19, 2026, 10:45 p.m. |
| PDg | Predicate description generation | batch_69e56702ad04819099c1c08f28d16809 |
completed | April 19, 2026, 11:36 p.m. |
Created at: April 11, 2026, 11:41 p.m.