Triple
T16551983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zealandia |
E402093
|
entity |
| Predicate | breakupApproxAge |
P52881
|
FINISHED |
| Object | "~80–100 million years ago" |
—
|
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: "~80–100 million years ago" | Statement: [Zealandia, breakupApproxAge, "~80–100 million years ago"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: breakupApproxAge Context triple: [Zealandia, breakupApproxAge, "~80–100 million years ago"]
-
A.
breakupDate
Indicates the date on which a romantic or partnership relationship between two entities ended.
-
B.
breakupTimeInterval
Indicates the time period during which a breakup between entities occurs or is in effect.
-
C.
breaksUpWith
Indicates that one entity ends a romantic or intimate relationship with another entity.
-
D.
approximateAgeBeforePresent
chosen
Indicates that one entity’s age is an estimated value measured as a time interval before the present moment.
-
E.
brokeUpIn
Indicates that a romantic or close relationship between entities ended in a specified location or context.
- F. None of above.
Provenance (3 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_69d88384bc30819084229e7dcdc39a41 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e34fc56f9081908bb8f6433a1a688d |
completed | April 18, 2026, 9:32 a.m. |
| PD | Predicate disambiguation | batch_69e296a47b7481909d9958158510c806 |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:15 a.m.