Triple
T23741269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Endurance interstellar mission |
E586678
|
entity |
| Predicate | includesRobot |
P48032
|
FINISHED |
| Object | TARS |
—
|
NE NERFINISHED |
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: TARS | Statement: [Endurance interstellar mission, includesRobot, TARS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesRobot Context triple: [Endurance interstellar mission, includesRobot, TARS]
-
A.
hasRobot
Indicates that one entity possesses, controls, or is associated with a robot.
-
B.
isRobotic
Indicates that an entity is robotic, meaning it is a robot or operates using robotic mechanisms or technology.
-
C.
hasRobotCharacterRole
Indicates that an entity participates in a role or function specifically as a robot character within a given context or work.
-
D.
hasOnboardRobot
chosen
Indicates that one entity (typically a vehicle, device, or platform) is equipped with or carries a robot on board.
-
E.
hasRobotCombination
Indicates a relationship where one entity is composed of, formed by, or associated with a specific combination of robots.
- 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_69e24908efb08190bf755c3a9b91f222 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1bad61d908190a0a8493bbba95d49 |
completed | April 29, 2026, 8:01 a.m. |
| PD | Predicate disambiguation | batch_69f155f012808190a4b1cbc155558ade |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 7:11 p.m.