Triple
T15807558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Big Bend Community College |
E383256
|
entity |
| Predicate | hasDurationOfMostPrograms |
P24633
|
FINISHED |
| Object | two years |
—
|
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: two years | Statement: [Big Bend Community College, hasDurationOfMostPrograms, two years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDurationOfMostPrograms Context triple: [Big Bend Community College, hasDurationOfMostPrograms, two years]
-
A.
programLength
chosen
Indicates the duration or total length of a program, typically measured in time or size.
-
B.
longestDurationAt
Indicates that one entity has the greatest length of time associated with a particular state, event, or activity compared to other relevant entities.
-
C.
hasLongRunningProgramming
Indicates that an entity is involved in or associated with programming activities that run or execute over an extended period of time.
-
D.
hasOfficialDuration
Indicates the formally defined length of time associated with an event, process, or entity.
-
E.
hasTypicalPerformanceDuration
Indicates the usual or expected length of time that a performance or activity typically lasts.
- 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_69d86da2858c819090cc8481e7207b6e |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0b52751348190964e82463ce9dd20 |
completed | April 16, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_69e0053b847c8190945726c3ddac21cc |
completed | April 15, 2026, 9:38 p.m. |
Created at: April 10, 2026, 4:48 a.m.