Triple
T8399497
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jesuit Ratio Studiorum |
E198135
|
entity |
| Predicate | dateFinalized |
P82025
|
FINISHED |
| Object | 1599 |
—
|
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: 1599 | Statement: [Jesuit Ratio Studiorum, dateFinalized, 1599]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateFinalized Context triple: [Jesuit Ratio Studiorum, dateFinalized, 1599]
-
A.
settledDate
Indicates the date on which a transaction, obligation, or agreement is fully completed and finalized.
-
B.
finalDeliveryDate
Indicates the date on which the last or ultimate delivery in a sequence of deliveries is scheduled or actually occurs.
-
C.
dateSigned
Indicates the specific date on which an agreement, document, or contract was formally signed.
-
D.
consolidationDate
Indicates the date on which multiple entities, records, or accounts are formally combined into a single consolidated whole.
-
E.
finalAppTransitionDate
Indicates the date on which the final transition or change of state for the application was completed.
- F. None of above. chosen
Provenance (4 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_69ca82f816bc8190ab321c07d72208c1 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb824ac29481909f02cdb2b7cd18af |
completed | March 31, 2026, 8:14 a.m. |
| PD | Predicate disambiguation | batch_69cb70d24b248190a326aa6804f942b5 |
completed | March 31, 2026, 6:59 a.m. |
| PDg | Predicate description generation | batch_69cb77690720819099de1e22b84a9563 |
completed | March 31, 2026, 7:27 a.m. |
Created at: March 30, 2026, 6:04 p.m.