Triple
T2706299
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NASA–ESA–CSA collaboration |
E59348
|
entity |
| Predicate | areaOfCooperation |
P26572
|
FINISHED |
| Object | space technology development |
—
|
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: space technology development | Statement: [NASA–ESA–CSA collaboration, areaOfCooperation, space technology development]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: areaOfCooperation Context triple: [NASA–ESA–CSA collaboration, areaOfCooperation, space technology development]
-
A.
collaborationArea
chosen
Indicates the domain, topic, or field in which two or more entities work together or collaborate.
-
B.
collaborationRegion
Indicates the geographic or administrative area within which the collaboration between entities takes place or is defined.
-
C.
thematicArea
Indicates the subject or item is associated with, or falls under, a particular thematic area or topic of focus.
-
D.
governanceArea
Indicates the geographic or jurisdictional area over which an entity has governing authority or responsibility.
-
E.
cooperationType
Indicates the specific kind or form of cooperative relationship that exists between the related 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_69ab4ac66bc88190b9e4afa5fc843f72 |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abda725f24819090e8d936b3d2d5bc |
completed | March 7, 2026, 7:57 a.m. |
| PD | Predicate disambiguation | batch_69abd82062988190b4292f242ad70b2c |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:55 p.m.