Triple
T6802545
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Codex Gregorianus |
E156219
|
entity |
| Predicate | compilerType |
P73095
|
FINISHED |
| Object | private jurist |
—
|
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: private jurist | Statement: [Codex Gregorianus, compilerType, private jurist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: compilerType Context triple: [Codex Gregorianus, compilerType, private jurist]
-
A.
compilationType
Indicates the specific method or mode by which something is compiled or assembled into a final form.
-
B.
compilerLanguage
Indicates that one entity is the programming language in which a given compiler is implemented.
-
C.
compilerOccupation
Indicates that one entity works as a compiler (e.g., of texts, data, or code) in relation to another entity, typically an organization, project, or work.
-
D.
codeType
Indicates the classification or category assigned to a particular code within a coding or encoding system.
-
E.
compiledUnder
Indicates that something (typically code or a program) was built or translated into executable form using a specific compiler, configuration, or compilation environment.
- 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_69c68826e6a48190a3d220b541e639de |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d2e714d4819084c8109c4de7de72 |
completed | March 27, 2026, 6:56 p.m. |
| PD | Predicate disambiguation | batch_69c6d099bf08819089a9f9894d037e74 |
completed | March 27, 2026, 6:46 p.m. |
| PDg | Predicate description generation | batch_69c6d2a8f9188190abbb8c730e7b5edf |
completed | March 27, 2026, 6:55 p.m. |
Created at: March 27, 2026, 2:16 p.m.