Triple
T23740504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Endurance (Interstellar spacecraft) |
E586658
|
entity |
| Predicate | associatedBlackHole |
P153515
|
FINISHED |
| Object | Gargantua |
—
|
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: Gargantua | Statement: [Endurance (Interstellar spacecraft), associatedBlackHole, Gargantua]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedBlackHole Context triple: [Endurance (Interstellar spacecraft), associatedBlackHole, Gargantua]
-
A.
roleInBlackHoles
Indicates the specific function, influence, or involvement an entity has in the formation, behavior, or study of black holes.
-
B.
hasSupermassiveBlackHole
Indicates that an astronomical object, such as a galaxy, contains or is associated with a supermassive black hole.
-
C.
centralBlackHoleName
Indicates the designated name assigned to a galaxy’s central black hole.
-
D.
massOfCentralBlackHole
Indicates the quantitative amount of mass possessed by the central black hole in a given system or context.
-
E.
associatedSpacetime
Indicates a relationship where an entity is linked to, or situated within, a particular spacetime region or context.
- 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_69e24908efb08190bf755c3a9b91f222 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1bad5209081909c44380816bec377 |
completed | April 29, 2026, 8:01 a.m. |
| PD | Predicate disambiguation | batch_69f155f012808190a4b1cbc155558ade |
completed | April 29, 2026, 12:50 a.m. |
| PDg | Predicate description generation | batch_69f15adb23d88190ac2632299c26a9b3 |
completed | April 29, 2026, 1:11 a.m. |
Created at: April 17, 2026, 7:11 p.m.