Triple
T31416902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Juris Doctor program at Duke Law School |
E801414
|
entity |
| Predicate | typicalDurationYears |
P75841
|
FINISHED |
| Object | 3 |
—
|
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: 3 | Statement: [Juris Doctor program at Duke Law School, typicalDurationYears, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalDurationYears Context triple: [Juris Doctor program at Duke Law School, typicalDurationYears, 3]
-
A.
typicalLengthUpperBoundYears
Indicates the maximum number of years that is typically expected for the length or duration of something.
-
B.
typicalLengthLowerBoundYears
Indicates the minimum number of years that typically characterizes the length or duration of something.
-
C.
typicalDurationDays
Indicates the usual or expected number of days that an associated event, process, or state typically lasts.
-
D.
typicalDurationMinutes
Indicates the usual or expected length of time, measured in minutes, that an event, activity, or process typically lasts.
-
E.
durationInYears
chosen
Indicates the length of time associated with something, measured in whole or fractional years.
- 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_69f348c26f048190b4adadd71b4596c5 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 30, 2026, 8:44 p.m.