Triple
T25956706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Materials Science Laboratory-2 |
E645422
|
entity |
| Predicate | conductedOn |
P159600
|
FINISHED |
| Object | Space Shuttle missions |
—
|
NE NERFINISHED |
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 Shuttle missions | Statement: [Materials Science Laboratory-2, conductedOn, Space Shuttle missions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conductedOn Context triple: [Materials Science Laboratory-2, conductedOn, Space Shuttle missions]
-
A.
conductedOnModule
Indicates that an activity, process, or operation is carried out on or within a specific module.
-
B.
convenedOn
Indicates that an event, meeting, or formal gathering took place or was held on a specific date or time.
-
C.
concludedAt
Indicates the point in time at which an event, process, or relationship comes to an end or is completed.
-
D.
concludedDuring
Indicates that an event, process, or state ended within the temporal bounds of another specified time period or event.
-
E.
dataCollectedOn
Indicates that certain data was gathered, recorded, or measured at a specific point in time or on a particular date.
- 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_69e77e85efc08190997da7fcf98bd300 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6049ef41c81908bace173136c2b00 |
completed | May 2, 2026, 2:05 p.m. |
| PD | Predicate disambiguation | batch_69f4a10480748190a2e67bd399fc435d |
completed | May 1, 2026, 12:48 p.m. |
| PDg | Predicate description generation | batch_69f55e497fa081909bc59a7b92c5df59 |
completed | May 2, 2026, 2:15 a.m. |
Created at: April 22, 2026, 8:46 a.m.