Triple
T25096592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hermogenianus |
E628604
|
entity |
| Predicate | legalTextCompiled |
P91332
|
FINISHED |
| Object | Codex Hermogenianus |
—
|
NE NERFINISHED |
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: Codex Hermogenianus | Statement: [Hermogenianus, legalTextCompiled, Codex Hermogenianus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalTextCompiled Context triple: [Hermogenianus, legalTextCompiled, Codex Hermogenianus]
-
A.
legalElement
Indicates that something is a constituent part or component required or recognized within a legal framework, rule, or process.
-
B.
legalContent
Indicates that the associated material complies with applicable laws and regulations and is permitted for use, distribution, or display.
-
C.
legalCorpus
chosen
Indicates that an entity is part of, contained in, or belongs to a body of legal texts, statutes, or case law used as a legal corpus.
-
D.
legalExpressionOf
Indicates a relationship where one entity is the formal legal articulation, representation, or codified form of another entity (such as a right, obligation, or agreement).
-
E.
legalCodeScript
Indicates that a legal code is written or represented using a particular writing system or script.
- 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_69e2ff2f58e881908340527bc5d34f07 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f6430a93a48190854ce71df680b2fa |
completed | May 2, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69f641da05b881909f6283c988639c53 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 18, 2026, 6:25 a.m.