Triple
T36560975
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apollo 13 Lunar Module Aquarius |
E901834
|
entity |
| Predicate | actuallyCarried |
P2774
|
FINISHED |
| Object | three astronauts during emergency |
—
|
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: three astronauts during emergency | Statement: [Apollo 13 Lunar Module Aquarius, actuallyCarried, three astronauts during emergency]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: actuallyCarried Context triple: [Apollo 13 Lunar Module Aquarius, actuallyCarried, three astronauts during emergency]
-
A.
carriedBy
chosen
Indicates that one entity is physically supported and transported by another entity.
-
B.
willCarry
Indicates that one entity is expected or intended to transport, bear, or convey another entity in the future.
-
C.
carriedAs
Indicates that one entity is transported or borne by another entity as its load or content.
-
D.
mayCarry
Indicates that one entity is permitted or able to transport, hold, or bear another entity.
-
E.
carriedTo
Indicates that one entity transported or conveyed another entity from one place to another.
- 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_69f76e634e9481908c9ba1b87ab87c26 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1baf25c8190a78dd54a400d2c50 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:11 p.m.