Triple
T26999057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 117 Days |
E680053
|
entity |
| Predicate | timeInConfinement |
P4499
|
FINISHED |
| Object | 117 days |
—
|
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: 117 days | Statement: [117 Days, timeInConfinement, 117 days]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeInConfinement Context triple: [117 Days, timeInConfinement, 117 days]
-
A.
hasResidenceTime
chosen
Indicates the duration for which something remains or stays within a particular place, system, or state.
-
B.
continuousHumanPresenceSince
Indicates that there has been an unbroken, ongoing human presence at or associated with the subject entity since the specified point in time.
-
C.
stayDurationFocus
Indicates the length of time an entity remains at or engaged with a particular place, activity, or context as the primary focus.
-
D.
hasVisitingTime
Indicates that there is a specified time period during which visits are allowed or scheduled for an entity.
-
E.
locationPeriod
Indicates that an entity is associated with being at a particular location during a specified 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_69eeeb52908c8190bd246244686aa455 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f62196f95c8190835dceee99f2082c |
completed | May 2, 2026, 4:08 p.m. |
| PD | Predicate disambiguation | batch_69f61b3ee7b08190a0a1bc5d26b757aa |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 6:56 a.m.