Triple
T8680250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Turbo-Union RB199 |
E206017
|
entity |
| Predicate | allianceDevelopment |
P600
|
FINISHED |
| Object | tri-national European collaboration |
—
|
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: tri-national European collaboration | Statement: [Turbo-Union RB199, allianceDevelopment, tri-national European collaboration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allianceDevelopment Context triple: [Turbo-Union RB199, allianceDevelopment, tri-national European collaboration]
-
A.
allianceUse
Indicates that one party makes use of, benefits from, or leverages an alliance or allied relationship with another party.
-
B.
alliance
chosen
Indicates a formal cooperative relationship between entities who agree to support each other in shared goals or interests.
-
C.
allianceCreated
Indicates that a formal cooperative relationship or partnership has been established between two or more parties.
-
D.
allianceHubFor
Indicates that one entity serves as a central coordinating hub or focal point for an alliance involving another entity.
-
E.
allianceType
Indicates the specific kind or category of alliance relationship that exists between entities.
- 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_69ca835379688190aa06b9d98e684d58 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc4ae6d19c8190be003f7901c0468d |
completed | March 31, 2026, 10:29 p.m. |
| PD | Predicate disambiguation | batch_69cc4567b5c881908d9ec5dcfc783fac |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:32 p.m.