Triple
T23631930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skylab Orbital Workshop |
E583633
|
entity |
| Predicate | totalCrewedOccupationTime |
P145205
|
FINISHED |
| Object | approximately 171 days |
—
|
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: approximately 171 days | Statement: [Skylab Orbital Workshop, totalCrewedOccupationTime, approximately 171 days]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: totalCrewedOccupationTime Context triple: [Skylab Orbital Workshop, totalCrewedOccupationTime, approximately 171 days]
-
A.
totalTimeOccupiedByCrew
chosen
Indicates the total duration of time that a crew occupies or is assigned to a particular task, resource, or location.
-
B.
crewEVAHours
Indicates the total number of hours that crew members spend performing extravehicular activities (spacewalks) outside their vehicle or habitat.
-
C.
totalCrewMembers
Indicates the total number of crew members associated with a given entity or context.
-
D.
timeInSpace
Indicates the amount of time an entity has spent in outer space.
-
E.
intendedCrew
Indicates that an entity is designated or planned to serve as the crew for another entity (such as a vehicle, mission, or operation).
- 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_69e248fe1c2c8190ac914d2442ff3d26 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b1e90a6881909f19b2446f9d54f0 |
completed | April 29, 2026, 7:23 a.m. |
| PD | Predicate disambiguation | batch_69f118d0e0588190a86527a7747c5427 |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:47 p.m.