Triple
T27549134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mir EO-23 |
E695442
|
entity |
| Predicate | nasaParticipation |
P75204
|
FINISHED |
| Object | Yes |
—
|
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: Yes | Statement: [Mir EO-23, nasaParticipation, Yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nasaParticipation Context triple: [Mir EO-23, nasaParticipation, Yes]
-
A.
spaceProgramInvolvement
Indicates that an entity is involved in, contributes to, or participates in a space exploration or space-related program.
-
B.
spaceAgencyCollaboration
Indicates a cooperative relationship in which space agencies work together on shared missions, projects, or objectives.
-
C.
roleInRelationToNASA
chosen
Indicates that one entity holds a specific role, position, or functional relationship with respect to NASA.
-
D.
NASAGroup
Indicates that the entities are associated through membership, affiliation, or grouping within NASA as an organization.
-
E.
spaceAgencyAffiliation
Indicates that one entity is formally affiliated with, operated by, or part of a particular space agency.
- 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_69ef5386c3e08190bfe33aa326e1f72b |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f62f877c988190928b6321c1f3f8f2 |
completed | May 2, 2026, 5:08 p.m. |
| PD | Predicate disambiguation | batch_69f62c1921008190a62675a31f66a875 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 1:34 p.m.