Triple
T6922797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Codex Hermogenianus |
E160227
|
entity |
| Predicate | legalGenre |
P73686
|
FINISHED |
| Object | codex of constitutions |
—
|
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: codex of constitutions | Statement: [Codex Hermogenianus, legalGenre, codex of constitutions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalGenre Context triple: [Codex Hermogenianus, legalGenre, codex of constitutions]
-
A.
genre
Indicates the artistic or thematic category to which a work (such as a book, film, or song) belongs.
-
B.
legalFiction
Indicates a relationship where something is treated as true or as having a particular legal status or effect, even though it is not literally or factually the case, for the purpose of applying or interpreting the law.
-
C.
genreDocumented
Indicates that a work’s genre has been formally recorded or documented.
-
D.
genreWithin
Indicates that one genre is a subgenre or more specific category contained within another, broader genre.
-
E.
genreRestriction
Indicates that there is a limitation or constraint on which genres are allowed or applicable in a given context.
- 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_69c6884d350081908d8a970e4d40ad78 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6d9fd159c819092a69d1a24e22dd5 |
completed | March 27, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69c6d7bb577c81908ee8b415b4281f3d |
completed | March 27, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69c6d98625c88190a37fdf6d95d7fcbd |
completed | March 27, 2026, 7:24 p.m. |
Created at: March 27, 2026, 2:26 p.m.