Triple
T12738372
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European Service Module |
E304422
|
entity |
| Predicate | collaborationFramework |
P1854
|
FINISHED |
| Object | ESA–NASA barter agreement |
—
|
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: ESA–NASA barter agreement | Statement: [European Service Module, collaborationFramework, ESA–NASA barter agreement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collaborationFramework Context triple: [European Service Module, collaborationFramework, ESA–NASA barter agreement]
-
A.
collaborationAspect
Indicates a specific characteristic, dimension, or feature of how entities collaborate or work together.
-
B.
collaborationModel
chosen
Indicates the type or structure of cooperative interaction or joint work established between entities.
-
C.
platformCollaboration
Indicates a collaborative relationship where multiple entities work together or integrate their efforts on or through a shared platform.
-
D.
collaborationOf
Indicates a relationship in which two or more entities work together jointly toward a shared goal or outcome.
-
E.
collaborationArea
Indicates the domain, topic, or field in which two or more entities work together or collaborate.
- 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_69d7bdf1426c8190a4402e1c4cdec33a |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96d89ea70819098c470344f172167 |
completed | April 10, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69d96403957c81909acdee7bdae71696 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:26 p.m.