Triple
T20946133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sphere of Jupiter |
E515847
|
entity |
| Predicate | positionInParadiso |
P141799
|
FINISHED |
| Object | sixth heaven |
—
|
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: sixth heaven | Statement: [Sphere of Jupiter, positionInParadiso, sixth heaven]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInParadiso Context triple: [Sphere of Jupiter, positionInParadiso, sixth heaven]
-
A.
positionOften
Indicates that one entity frequently holds, occupies, or is located at a particular position relative to another entity or context.
-
B.
positionOnEuro
Indicates that an entity holds a specific official role or position within the institutions or organizational structure of the European Union.
-
C.
positionInCase
Indicates the specific role, status, or placement that an entity holds within a particular case or legal proceeding.
-
D.
positionOnEstablishment
Indicates the spatial or functional placement of one entity relative to an establishment (such as being located on, within, or as part of that establishment).
-
E.
positionEstablishedIn
Indicates the point in time or event when a particular position, role, or office was formally created or instituted.
- 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_69e0b4fcd678819087a304291f14330a |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6fad7f67481908675e76736f5e0c3 |
completed | April 21, 2026, 4:19 a.m. |
| PD | Predicate disambiguation | batch_69e5c9b1bae48190a845165fed1b005e |
completed | April 20, 2026, 6:37 a.m. |
| PDg | Predicate description generation | batch_69e5d53d22d08190bc17ed4bed53804a |
completed | April 20, 2026, 7:26 a.m. |
Created at: April 16, 2026, 12:56 p.m.