Triple
T33985161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CST |
E871391
|
entity |
| Predicate | roleInCNES |
P202734
|
FINISHED |
| Object | main technical center |
—
|
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: main technical center | Statement: [CST, roleInCNES, main technical center]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInCNES Context triple: [CST, roleInCNES, main technical center]
-
A.
roleInISRO
Indicates that an entity holds or has held a specific role, position, or responsibility within the Indian Space Research Organisation (ISRO).
-
B.
roleInRelationToNASA
Indicates that one entity holds a specific role, position, or functional relationship with respect to NASA.
-
C.
roleInJamesWebbSpaceTelescope
Indicates that an entity holds or held a specific role or position in relation to the James Webb Space Telescope project or mission.
-
D.
operatorOfSpaceMission
Indicates that one entity is the organization or individual responsible for operating or managing a specific space mission.
-
E.
roleInCubeSat
Indicates that an entity holds a specific functional role or responsibility within the context of a CubeSat mission or project.
- 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_69f3499e964c8190b674b03f6f791b4b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a00b2b425a8819091ff65695e98c3af |
completed | May 10, 2026, 4:30 p.m. |
| PD | Predicate disambiguation | batch_6a00b06efa248190b2d16b4889185119 |
completed | May 10, 2026, 4:21 p.m. |
| PDg | Predicate description generation | batch_6a00b2b3832c8190a1cb63e2a55639eb |
completed | May 10, 2026, 4:30 p.m. |
Created at: May 1, 2026, 1:50 a.m.