Triple
T25096598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hermogenianus |
E628604
|
entity |
| Predicate | hasWorkInCorpusIurisCivilis |
P167039
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Hermogenianus, hasWorkInCorpusIurisCivilis, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWorkInCorpusIurisCivilis Context triple: [Hermogenianus, hasWorkInCorpusIurisCivilis, yes]
-
A.
haveCivilLaw
Indicates that an entity is subject to, governed by, or operates under a civil law legal system.
-
B.
hasPartInJurisprudence
Indicates that one legal concept, rule, or component forms a constituent part of another within the domain of jurisprudence.
-
C.
hasJurisprudenceField
Indicates that an entity’s work, expertise, or classification pertains to a specific field or branch of jurisprudence (legal theory or law).
-
D.
involvedInLegalDoctrine
Indicates that an entity plays a role in the formation, interpretation, application, or development of a particular legal doctrine.
-
E.
jurisprudenceDiscussedIn
Indicates that a topic, issue, or principle of jurisprudence is examined, analyzed, or debated within a particular document, discussion, or source.
- 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_69e2ff2f58e881908340527bc5d34f07 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f6653ccf648190b65fb1141928e47e |
completed | May 2, 2026, 8:57 p.m. |
| PD | Predicate disambiguation | batch_69f6633451948190bcc0410602bb4914 |
completed | May 2, 2026, 8:48 p.m. |
| PDg | Predicate description generation | batch_69f663ff176c8190aaadb475f75daee4 |
completed | May 2, 2026, 8:52 p.m. |
Created at: April 18, 2026, 6:25 a.m.