Triple
T35290090
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | approve annual operating budget of The College of New Jersey |
E1019196
|
entity |
| Predicate | timeAppliesTo |
P302
|
FINISHED |
| Object | fiscal year |
—
|
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: fiscal year | Statement: [approve annual operating budget of The College of New Jersey, timeAppliesTo, fiscal year]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeAppliesTo Context triple: [approve annual operating budget of The College of New Jersey, timeAppliesTo, fiscal year]
-
A.
meetsInTimePeriod
Indicates that two entities encounter or come together during a specified time period.
-
B.
appliedDuringPeriod
Indicates that an action, condition, or status was in effect throughout a specified time period.
-
C.
appliesAt
Indicates that an action, rule, or condition is relevant to or in effect at a specific location, context, or point in time.
-
D.
timePeriodQualifier
Indicates how a time-related statement or value is further specified or constrained, such as by defining its scope, phase, or contextual condition within a broader time period.
-
E.
timePeriod
chosen
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
- 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_69f76de6d39c8190bb11342e4b91ff2b |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f79012e2e481908c587ff189b3deb3 |
completed | May 3, 2026, 6:12 p.m. |
| PD | Predicate disambiguation | batch_69f78e2f52e08190a77661223a96c601 |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:03 p.m.