Triple
T12139617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anne Heche |
E289147
|
entity |
| Predicate | endTimeOfPartner |
P86224
|
FINISHED |
| Object | 2000 |
—
|
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: 2000 | Statement: [Anne Heche, endTimeOfPartner, 2000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endTimeOfPartner Context triple: [Anne Heche, endTimeOfPartner, 2000]
-
A.
endTimeAsConsort
Indicates the point in time when an individual's role or status as a consort to another person comes to an end.
-
B.
typicallyEndsAt
Indicates that an event, process, or activity most commonly or usually concludes at a particular time, place, or state.
-
C.
endTimeAsCapital
Indicates that a specified time marks the ending point of an event, process, or state in the role of its designated capital or primary endpoint.
-
D.
holderEndDate
Indicates the date on which an entity’s role as holder of something (e.g., an asset, position, or right) comes to an end.
-
E.
endTimeOfRole
chosen
Indicates the point in time at which a particular role or position held by an entity concludes.
- 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_69d6ab4b5e4c81909950b17151eb0951 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d91841615c819097f20a7447a1b8f4 |
completed | April 10, 2026, 3:33 p.m. |
| PD | Predicate disambiguation | batch_69d91508f8008190b3a90ec0bf0953ca |
completed | April 10, 2026, 3:19 p.m. |
Created at: April 8, 2026, 9:49 p.m.