Triple
T15872242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tapping Reeve House and Law School |
E384857
|
entity |
| Predicate | lawSchoolFounded |
P75018
|
FINISHED |
| Object | 1784 |
—
|
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: 1784 | Statement: [Tapping Reeve House and Law School, lawSchoolFounded, 1784]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lawSchoolFounded Context triple: [Tapping Reeve House and Law School, lawSchoolFounded, 1784]
-
A.
legalSchoolFoundedIn
chosen
Indicates that a law school was established or came into existence in a specific year or time period.
-
B.
lawSchoolName
Indicates the name of the law school with which an entity (such as a person or institution) is associated.
-
C.
majorSchoolOfLaw
Indicates that a particular school of law is a primary or dominant legal tradition or framework associated with an entity.
-
D.
hasLegalEducationInstitution
Indicates that an entity is associated with or linked to an institution that provides legal education.
-
E.
schoolOfJurisprudence
Indicates that one entity is a legal philosophy, doctrine, or interpretive framework to which the other entity (such as a jurist, decision, or institution) adheres or belongs.
- 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_69d86da4e86481909f1325fdc971b5ec |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e174de2cd48190ab18e48c9f051a2a |
completed | April 16, 2026, 11:46 p.m. |
| PD | Predicate disambiguation | batch_69e142c3e18c8190bb7b023f4a0eaebb |
completed | April 16, 2026, 8:12 p.m. |
Created at: April 10, 2026, 4:51 a.m.