Triple
T20906737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brigham Young University–Idaho |
E514819
|
entity |
| Predicate | hasCalendarSystemFeature |
P97978
|
FINISHED |
| Object | Fall track |
—
|
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: Fall track | Statement: [Brigham Young University–Idaho, hasCalendarSystemFeature, Fall track]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCalendarSystemFeature Context triple: [Brigham Young University–Idaho, hasCalendarSystemFeature, Fall track]
-
A.
hasCalendarFunction
Indicates that an entity possesses or supports a calendar-related capability or functionality.
-
B.
usedInCalendarSystem
chosen
Indicates that something (such as a time unit, era, or convention) is employed as part of a particular calendar system.
-
C.
hasFeature
Indicates that an entity possesses, exhibits, or includes a particular characteristic, attribute, or component.
-
D.
hasFeatureCode
Indicates that an entity is associated with a specific feature identifier or code that characterizes one of its properties or attributes.
-
E.
isPartOfSystemWithFeature
Indicates that one entity belongs to a system that possesses a specified feature or characteristic.
- 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_69e0b4f8a1108190bce3d31331290ced |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6e9001a8c81909fa1004b5977d04f |
completed | April 21, 2026, 3:03 a.m. |
| PD | Predicate disambiguation | batch_69e5c9ac91108190a6700fcdf2f11890 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:47 p.m.