Triple
T16690337
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Doe (Se7en) |
E405576
|
entity |
| Predicate | plansDuration |
P40755
|
FINISHED |
| Object | over a year (implied long-term planning) |
—
|
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: over a year (implied long-term planning) | Statement: [John Doe (Se7en), plansDuration, over a year (implied long-term planning)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plansDuration Context triple: [John Doe (Se7en), plansDuration, over a year (implied long-term planning)]
-
A.
possibleDuration
Indicates the range or specific length of time that an action, event, or state can last or is allowed to last.
-
B.
projectLength
Indicates the duration or total time span over which a project is planned or executed.
-
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.
offersDuration
Indicates that an entity provides or specifies a length of time for which something (such as a service, offer, or condition) is available or valid.
-
E.
banDurationApproximate
Indicates that the duration of a ban is known only approximately rather than as an exact, precise time period.
- 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_69d8838c28748190b3f5967c743940ab |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37ea8cabc8190ba321503399960da |
completed | April 18, 2026, 12:52 p.m. |
| PD | Predicate disambiguation | batch_69e319bc73908190a0e38bc926b31f10 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:19 a.m.