Triple
T36485368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | US Lab |
E898919
|
entity |
| Predicate | roleOnISS |
P110710
|
FINISHED |
| Object | primary American research module |
—
|
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: primary American research module | Statement: [US Lab, roleOnISS, primary American research module]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleOnISS Context triple: [US Lab, roleOnISS, primary American research module]
-
A.
crewMemberInOrbit
Indicates that a person is serving as a crew member aboard a spacecraft or station that is currently in orbit.
-
B.
positionOnISS
Indicates that one entity occupies a specific location or role on the International Space Station relative to other entities or reference points.
-
C.
spaceStationRole
chosen
Indicates the functional role or duty an entity has in relation to a space station.
-
D.
isAstronautOf
Indicates that a person serves as an astronaut who is a member of, or assigned to, a particular space agency, mission, or spacecraft.
-
E.
attachedToSpaceStation
Indicates that an object is physically connected or secured to a space station.
- 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_69f76e5ad4588190bdbce60c52fbb785 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fcda3699948190adb57625bae08091 |
completed | May 7, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fd16d08190b0aca6e19a632e99 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:10 p.m.