Triple
T1688953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STS-114 |
E36506
|
entity |
| Predicate | evaPurpose |
P30831
|
FINISHED |
| Object | ISS maintenance and external experiments installation |
—
|
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: ISS maintenance and external experiments installation | Statement: [STS-114, evaPurpose, ISS maintenance and external experiments installation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: evaPurpose Context triple: [STS-114, evaPurpose, ISS maintenance and external experiments installation]
-
A.
eve
Indicates a relationship where one entity is the evening or night-time counterpart, phase, or occurrence associated with another entity.
-
B.
EVAobjective
chosen
Indicates that an extravehicular activity (EVA) is performed with the purpose of achieving a specific objective or goal.
-
C.
damPurpose
Indicates the primary function or intended use for which a dam has been constructed or is operated.
-
D.
evaCount
Indicates a relationship where a specific count or number is associated with an evaluation-related event, action, or occurrence.
-
E.
purpose
Indicates that one entity exists, is done, or is used in order to achieve, support, or serve the goal, function, or intended outcome of another entity.
- 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_69a886151508819084fa7f1ce6e05577 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aaf3359ce48190803b322db8ad6027 |
completed | March 6, 2026, 3:31 p.m. |
| PD | Predicate disambiguation | batch_69aa61b71cec8190b273588051058ebd |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:29 p.m.