Triple
T32198403
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman province of Noricum |
E822461
|
entity |
| Predicate | divisionDateApprox |
P877
|
FINISHED |
| Object | late 3rd century 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: late 3rd century AD | Statement: [Roman province of Noricum, divisionDateApprox, late 3rd century AD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: divisionDateApprox Context triple: [Roman province of Noricum, divisionDateApprox, late 3rd century AD]
-
A.
divisionYear
Indicates the year in which a division or split of an entity took place.
-
B.
divisionSince
Indicates that one entity has been divided or split from another starting at a specific point in time.
-
C.
dateApproximate
chosen
Indicates that the associated date is not exact but estimated or approximate rather than precisely known.
-
D.
divisionFrequency
Indicates how often a division event occurs within a given context or time frame.
-
E.
divisionAlsoKnownAs
Indicates that one division is alternatively referred to by another name or alias.
- 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_69f349093174819086e633c190a51aa8 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bb396ae081908d519ffc46252b1f |
completed | May 3, 2026, 3:04 a.m. |
| PD | Predicate disambiguation | batch_69f6b3aa892481908d29283a074e6722 |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:36 a.m.