Triple
T26109449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Max Dugan |
E658643
|
entity |
| Predicate | returnsAfter |
P45021
|
FINISHED |
| Object | long absence |
—
|
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 absence | Statement: [Max Dugan, returnsAfter, long absence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: returnsAfter Context triple: [Max Dugan, returnsAfter, long absence]
-
A.
returns
Indicates that one entity gives or sends something back to another entity, often as a result or outcome of a process or action.
-
B.
returnsAs
Indicates that one entity goes back to or resumes a previous state, location, role, or condition associated with another entity.
-
C.
returnedFor
Indicates that an entity has been sent, given, or brought back in response to, or on behalf of, another entity or prior action.
-
D.
returnsFor
Indicates that an entity goes back to a previous place, state, or counterpart, typically reversing or completing an earlier departure or action.
-
E.
returnsTo
chosen
Indicates that an entity goes back to a previous location, state, or entity it was associated with before.
- 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_69ee5bc20298819099a42be042eb2349 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f6077b10108190b1842436b70f8985 |
completed | May 2, 2026, 2:17 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fd90fc81909055b211368f9139 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 8:01 p.m.