Triple
T5624418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skylab 2 |
E147684
|
entity |
| Predicate | EVAtime |
P65491
|
FINISHED |
| Object | about 6 hours 20 minutes total |
—
|
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: about 6 hours 20 minutes total | Statement: [Skylab 2, EVAtime, about 6 hours 20 minutes total]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: EVAtime Context triple: [Skylab 2, EVAtime, about 6 hours 20 minutes total]
-
A.
nearbyTransit
Indicates that one location has public transportation options situated within a short distance or easy access from it.
-
B.
roadClosesIn
Indicates that a road becomes closed or inaccessible within a specified location, area, or boundary.
-
C.
hasApproximateWalkingTimeTo
Indicates that there is an estimated or approximate amount of time it takes to walk from one entity to another.
-
D.
hasCommuterTraffic
Indicates that there is regular, recurring traffic flow associated with people traveling between their homes and places of work or study.
-
E.
travelTimeCategory
Indicates the qualitative classification of how long a given travel or trip duration is (e.g., short, medium, long).
- 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_69c00906f2a88190a992c66b13d606d4 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c022165d8c8190b2a14f1cd0a45ecc |
completed | March 22, 2026, 5:08 p.m. |
| PD | Predicate disambiguation | batch_69c01b1d4b108190846ce586dc783acf |
completed | March 22, 2026, 4:38 p.m. |
| PDg | Predicate description generation | batch_69c01f40df64819089a659ea00a835ef |
completed | March 22, 2026, 4:56 p.m. |
Created at: March 22, 2026, 3:40 p.m.