Triple
T21745082
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orbital Workshop |
E536765
|
entity |
| Predicate | endOfCrewedUse |
P145204
|
FINISHED |
| Object | 1974-02-08 |
—
|
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: 1974-02-08 | Statement: [Orbital Workshop, endOfCrewedUse, 1974-02-08]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endOfCrewedUse Context triple: [Orbital Workshop, endOfCrewedUse, 1974-02-08]
-
A.
lastCrewReturnDate
Indicates the date on which the most recent crew associated with the entity returned.
-
B.
militaryUseEnd
Indicates the point in time or condition at which the military use of something (such as a facility, resource, or asset) ceases.
-
C.
lastCrewedUndockingDate
Indicates the calendar date on which the most recent undocking event occurred that involved a crewed vehicle.
-
D.
lastCrewedLaunchDate
Indicates the calendar date on which the most recent crewed launch associated with the subject took place.
-
E.
endTimeOfUseAsResearchVessel
Indicates the point in time when something’s role or function as a research vessel comes to an end.
- 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_69e0c46df5448190b4322127ffc4c690 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f01a75352c8190bcd46759562ee251 |
completed | April 28, 2026, 2:24 a.m. |
| PD | Predicate disambiguation | batch_69e6969c16fc8190b5126c169317d85d |
completed | April 20, 2026, 9:11 p.m. |
| PDg | Predicate description generation | batch_69e69f3ed4408190a4a78410bf660c44 |
completed | April 20, 2026, 9:48 p.m. |
Created at: April 16, 2026, 6:49 p.m.