Triple
T16831437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Titius–Bode law |
E409157
|
entity |
| Predicate | predictsPoorly |
P125015
|
FINISHED |
| Object | orbit of Neptune |
—
|
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: orbit of Neptune | Statement: [Titius–Bode law, predictsPoorly, orbit of Neptune]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predictsPoorly Context triple: [Titius–Bode law, predictsPoorly, orbit of Neptune]
-
A.
predictedIn
Indicates that something has been forecast, anticipated, or estimated to occur within or as part of a specified context, time, or situation.
-
B.
predictionType
Indicates the kind or category of prediction being made about an entity or event.
-
C.
predictionBy
Indicates that one entity serves as the source or author of a prediction made about another entity or outcome.
-
D.
predictability
Indicates that the outcome, behavior, or result of one entity in relation to another can be reliably anticipated or forecast based on known patterns or information.
-
E.
misjudges
Indicates that one entity forms an incorrect or unfair opinion or assessment about another entity or situation.
- 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_69d883952b048190887740a980b712ed |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b317af8c8190a09cb6d60d28e342 |
completed | April 18, 2026, 4:36 p.m. |
| PD | Predicate disambiguation | batch_69e32b87b4248190aaddb05e88452356 |
completed | April 18, 2026, 6:58 a.m. |
| PDg | Predicate description generation | batch_69e34fb7c8c8819086975b7955b7d8ef |
completed | April 18, 2026, 9:32 a.m. |
Created at: April 10, 2026, 5:23 a.m.