Triple
T7225844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Army Institute of Law |
E154775
|
entity |
| Predicate | academicDomain |
P778
|
FINISHED |
| Object | law and legal studies |
—
|
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: law and legal studies | Statement: [Army Institute of Law, academicDomain, law and legal studies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: academicDomain Context triple: [Army Institute of Law, academicDomain, law and legal studies]
-
A.
academicFocus
chosen
Indicates the primary field of study, discipline, or subject area that an entity concentrates on academically.
-
B.
academicContext
Indicates the educational or scholarly setting, framework, or circumstances within which an activity, relationship, or piece of information takes place.
-
C.
academicType
Indicates the specific academic category or classification associated with an entity (such as a work, program, or role).
-
D.
housesAcademicDiscipline
Indicates that an entity serves as the location or institutional home where a particular academic discipline is based, organized, or conducted.
-
E.
academicUse
Indicates that something is intended for, suitable for, or used within an academic or educational context.
- 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_69c68811dd1c8190ac460bb39e64e1f0 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6e9dc835881909ea646c392a980b6 |
completed | March 27, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69c6e761b7fc8190857794d78af1b468 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 2:54 p.m.