Triple
T3971493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Easter hotspot |
E92344
|
entity |
| Predicate | activityDuration |
P40755
|
FINISHED |
| Object | long-term geological timescales |
—
|
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: long-term geological timescales | Statement: [Easter hotspot, activityDuration, long-term geological timescales]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: activityDuration Context triple: [Easter hotspot, activityDuration, long-term geological timescales]
-
A.
activityTime
Indicates the time period during which an activity occurs or is scheduled to take place.
-
B.
activityStartApprox
Indicates that the start time of an activity is known only approximately, rather than as an exact timestamp.
-
C.
intendedDuration
chosen
Indicates the planned or expected length of time for which an action, event, or state is meant to occur or remain in effect.
-
D.
occupationDuration
Indicates the length of time an entity holds or has held a particular occupation or role.
-
E.
peakActivity
Indicates that an entity is at its highest or most intense level of activity within a given period 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_69aed96624188190ac8c45bb57ab72b5 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefaca33e4819091957c7915857a42 |
completed | March 9, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69aef8f252b081909749d40440d372b2 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:32 p.m.