Triple
T23740767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gargantua |
E586664
|
entity |
| Predicate | eventHorizonShape |
P153518
|
FINISHED |
| Object | distorted by rapid spin |
—
|
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: distorted by rapid spin | Statement: [Gargantua, eventHorizonShape, distorted by rapid spin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eventHorizonShape Context triple: [Gargantua, eventHorizonShape, distorted by rapid spin]
-
A.
eventHorizonType
Indicates the specific kind or classification of an event horizon associated with a given object or phenomenon.
-
B.
hasEventHorizon
Indicates that an object possesses an event horizon, a boundary beyond which events cannot affect an outside observer.
-
C.
horizonStructure
Indicates the structural or organizational characteristics that define how a horizon or boundary layer is formed, arranged, or composed.
-
D.
spacecraftShape
Indicates the geometric form or physical configuration that a spacecraft possesses.
-
E.
domeShape
Indicates that one entity has a dome-like or hemispherical shape in relation to another or in its overall form.
- 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_69f1bad61d908190a0a8493bbba95d49 |
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.