Triple
T21130401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Space Station expedition |
E520668
|
entity |
| Predicate | hasCrewSizeRange |
P883
|
FINISHED |
| Object | typically 3 to 10 people |
—
|
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: typically 3 to 10 people | Statement: [International Space Station expedition, hasCrewSizeRange, typically 3 to 10 people]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCrewSizeRange Context triple: [International Space Station expedition, hasCrewSizeRange, typically 3 to 10 people]
-
A.
hasCrewCapacity
Indicates that an entity is capable of accommodating a specified number of crew members.
-
B.
hasCrewFeature
Indicates that a crew possesses or is characterized by a particular feature, attribute, or capability.
-
C.
hasExtendedCrew
Indicates that an entity is associated with an additional or supplementary group of crew members beyond its primary crew.
-
D.
crewCountApproximate
chosen
Indicates that the relationship specifies an estimated or approximate number of crew members associated with an entity.
-
E.
crewCount
Indicates the number of crew members associated with an entity, such as a vehicle, vessel, or mission.
- 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_69e0b50b53048190ae34e8abbe3c5ada |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e723556ec08190a2ade96c76f9cec7 |
completed | April 21, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69e5f5ed6c8c8190b31092a5d4c3de5d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 2:56 p.m.