Triple
T20273767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Møre Margin |
E502957
|
entity |
| Predicate | majorBreakupPhase |
P139508
|
FINISHED |
| Object | Paleogene |
—
|
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: Paleogene | Statement: [Møre Margin, majorBreakupPhase, Paleogene]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorBreakupPhase Context triple: [Møre Margin, majorBreakupPhase, Paleogene]
-
A.
majorBreakupEvent
Indicates a significant romantic relationship ending between entities, typically marking a pivotal or impactful breakup event.
-
B.
majorPhase
Indicates that one phase is a primary or dominant stage within a larger process, lifecycle, or sequence.
-
C.
breakupProcess
Indicates the process by which a relationship or union between entities is dissolved, including the steps or phases leading to their separation.
-
D.
breakup
Indicates the ending or dissolution of a romantic or close personal relationship between two entities.
-
E.
majorPhaseCompletion
Indicates that a significant or primary phase of a larger process, project, or lifecycle has been fully completed.
- 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_69e0b4b0e79c8190bd61f22ef1329fa8 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e675e104f081909d17c1963a5db528 |
completed | April 20, 2026, 6:52 p.m. |
| PD | Predicate disambiguation | batch_69e55b1e5e1c8190ba8a5544b1db9e1d |
completed | April 19, 2026, 10:45 p.m. |
| PDg | Predicate description generation | batch_69e56702ad04819099c1c08f28d16809 |
completed | April 19, 2026, 11:36 p.m. |
Created at: April 16, 2026, 10:28 a.m.