Triple
T32239865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | West Los Angeles College |
E823579
|
entity |
| Predicate | hasDurationOfTypicalProgram |
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: [West Los Angeles College, hasDurationOfTypicalProgram, two years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDurationOfTypicalProgram Context triple: [West Los Angeles College, hasDurationOfTypicalProgram, two years]
-
A.
hasTypicalPerformanceDuration
Indicates the usual or expected length of time that a performance or activity typically lasts.
-
B.
programLength
chosen
Indicates the duration or total length of a program, typically measured in time or size.
-
C.
typicalViewingTime
Indicates the usual or most common amount of time an entity is viewed or watched under normal circumstances.
-
D.
typicalMasterDuration
Indicates the usual or standard length of time for which a master (e.g., a primary or controlling entity) remains in effect or holds its role.
-
E.
typicalRecordingDuration
Indicates the usual or standard length of time that something is recorded.
- 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_69f3490c140481908ed53b98b561eaa1 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bc2f34f88190ae24a9bba5e6c8ec |
completed | May 3, 2026, 3:08 a.m. |
| PD | Predicate disambiguation | batch_69f6b632cf788190a3d0c08cd026b84b |
completed | May 3, 2026, 2:42 a.m. |
Created at: May 1, 2026, 12:39 a.m.