Triple
T5051117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phobos |
E113785
|
entity |
| Predicate | willLikelyBreakUpIn |
P60888
|
FINISHED |
| Object | tens of millions of years |
—
|
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: tens of millions of years | Statement: [Phobos, willLikelyBreakUpIn, tens of millions of years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: willLikelyBreakUpIn Context triple: [Phobos, willLikelyBreakUpIn, tens of millions of years]
-
A.
breaksUpWith
Indicates that one entity ends a romantic or intimate relationship with another entity.
-
B.
plannedBreakupAnnounced
Indicates that a previously intended or scheduled breakup between parties has been publicly or explicitly announced.
-
C.
breakupLinkedTo
Indicates a causal or associative relationship where a breakup is connected to, influenced by, or results from another event, factor, or entity.
-
D.
brokenUp
Indicates that a previously existing romantic or close relationship between two entities has ended.
-
E.
breakupDate
Indicates the date on which a romantic or partnership relationship between two entities ended.
- 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_69bd443aa1f88190abb992d138f2cf42 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd7426fc8081908a8227f73168c235 |
completed | March 20, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69bd715479f08190933604aebd34414f |
completed | March 20, 2026, 4:09 p.m. |
| PDg | Predicate description generation | batch_69bd73089f548190834103366e24ab40 |
completed | March 20, 2026, 4:17 p.m. |
Created at: March 20, 2026, 1:37 p.m.