Triple
T26317270
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NCAA Division III |
E662004
|
entity |
| Predicate | timeDemands |
P100973
|
FINISHED |
| Object | lower than Division I and many Division II programs |
—
|
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: lower than Division I and many Division II programs | Statement: [NCAA Division III, timeDemands, lower than Division I and many Division II programs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeDemands Context triple: [NCAA Division III, timeDemands, lower than Division I and many Division II programs]
-
A.
timeToComplete
Indicates the duration required for an entity or process to be fully completed.
-
B.
time
Indicates a temporal relationship specifying when an event occurs or how entities are ordered or related in time.
-
C.
durationRequirement
Indicates that a specified action, process, or state must persist for at least a certain length of time to satisfy a condition or rule.
-
D.
timeProfile
Indicates the temporal pattern or schedule according to which an action, process, or relationship occurs or is distributed over time.
-
E.
timeSensitivity
chosen
Indicates how strongly the relationship or action depends on, changes with, or is constrained by time.
- 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_69ee812e73048190aae587f1d51e5a06 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f60f28e9588190b76581e150f4f27d |
completed | May 2, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69f5f7ff548c8190a23e98c5e66e0bc7 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 10:25 p.m.