Triple
T11638210
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CollegePass |
E276580
|
entity |
| Predicate | typicalValidity |
P82112
|
FINISHED |
| Object | academic term |
—
|
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: academic term | Statement: [CollegePass, typicalValidity, academic term]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalValidity Context triple: [CollegePass, typicalValidity, academic term]
-
A.
validityType
Indicates the specific kind or category of validity that characterizes how or under what conditions something is considered valid.
-
B.
validityRegime
chosen
Indicates the set of conditions, rules, or context under which something (such as a statement, document, or status) is considered valid or in force.
-
C.
typicalEndDate
Indicates the date on which something, such as an event, process, or period, normally or customarily ends.
-
D.
validityArea
Indicates the geographic or contextual area within which something (such as a rule, document, or status) is considered valid or in effect.
-
E.
typicalPeriod
Indicates the usual or characteristic time interval or duration associated with an event, process, or state.
- 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_69d6aafa51148190ab84940694c00235 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a25e90c08190b7fb73939a2be3d7 |
completed | April 10, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69d85dd94bdc819091fa2ed33eb31624 |
completed | April 10, 2026, 2:18 a.m. |
Created at: April 8, 2026, 9:39 p.m.