Triple
T2162931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | University of Miami School of Law |
E46840
|
entity |
| Predicate | hasCalendarSystem |
P17591
|
FINISHED |
| Object | semester system |
—
|
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: semester system | Statement: [University of Miami School of Law, hasCalendarSystem, semester system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCalendarSystem Context triple: [University of Miami School of Law, hasCalendarSystem, semester system]
-
A.
usesJulianCalendar
Indicates that the subject follows or is based on the Julian calendar system for dating events or timekeeping.
-
B.
hasDayNameSystem
Indicates that an entity employs or is associated with a particular system for naming or designating days.
-
C.
hasNumberSystem
Indicates that an entity possesses or uses a particular system for representing and organizing numbers.
-
D.
usesClockSystem
Indicates that one entity employs or operates according to the clock or timekeeping system defined or provided by another entity.
-
E.
hasCalendarCustom
chosen
Indicates that an entity is associated with a customized or non-default calendar configuration or behavior.
- 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_69a88a184cbc8190877791f6552c2484 |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abbe8d105c819098371c35c88873dc |
completed | March 7, 2026, 5:58 a.m. |
| PD | Predicate disambiguation | batch_69abbd9c90408190b6b65498ca43ce26 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:45 p.m.