Triple
T8438299
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Digest of Justinian |
E199284
|
entity |
| Predicate | sourceMaterialFrom |
P53073
|
FINISHED |
| Object | classical Roman jurists of 1st–3rd centuries AD |
—
|
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: classical Roman jurists of 1st–3rd centuries AD | Statement: [Digest of Justinian, sourceMaterialFrom, classical Roman jurists of 1st–3rd centuries AD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sourceMaterialFrom Context triple: [Digest of Justinian, sourceMaterialFrom, classical Roman jurists of 1st–3rd centuries AD]
-
A.
sourceMaterialType
Indicates the type or category of material from which something originates or is derived.
-
B.
materialSource
chosen
Indicates that one entity serves as the origin or provider of the material or substance used by another entity.
-
C.
hasSourceMaterial
Indicates that something is derived from, based on, or created using a particular source material.
-
D.
featuresMaterialFrom
Indicates that one entity incorporates, contains, or is composed of material originating from another entity.
-
E.
source
Indicates that something originates from, is derived from, or is provided by a particular entity or location.
- 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_69ca8314cd6c8190a6b8c2a1096e18f3 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe30fba4081908bfdef3faf5baceb |
completed | March 31, 2026, 3:06 p.m. |
| PD | Predicate disambiguation | batch_69cbd0f5a3648190beb53a139a2d5482 |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:08 p.m.