Triple
T31065079
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anicia Juliana |
E791643
|
entity |
| Predicate | placeOfViennaDioscuridesProduction |
P184612
|
FINISHED |
| Object | Constantinople |
—
|
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: Constantinople | Statement: [Anicia Juliana, placeOfViennaDioscuridesProduction, Constantinople]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: placeOfViennaDioscuridesProduction Context triple: [Anicia Juliana, placeOfViennaDioscuridesProduction, Constantinople]
-
A.
manuscriptDiscoveredBy
Indicates that a manuscript was found or brought to light through the efforts or actions of a particular agent or entity.
-
B.
discoveredInAntiquity
Indicates that something was found, identified, or recognized during ancient historical times rather than in the modern era.
-
C.
manuscriptFoundIn
Indicates that a manuscript is discovered or located within a particular place, collection, or context.
-
D.
CopernicusWorkedIn
Indicates that Copernicus carried out his professional or scholarly work in a specified place or institution.
-
E.
flourishedIn
Indicates that an entity experienced its peak activity, success, or prominence during a specified time period or era.
- 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_69f224cc0c5c81908404f087bff92997 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7b365288c8190bcb11fcfba028737 |
completed | May 3, 2026, 8:43 p.m. |
| PD | Predicate disambiguation | batch_69f7b1b8a9fc8190a1279e67a2d12707 |
completed | May 3, 2026, 8:36 p.m. |
| PDg | Predicate description generation | batch_69f7b2f2b9ac8190aa05b8a1aa18ec2d |
completed | May 3, 2026, 8:41 p.m. |
Created at: April 29, 2026, 9:01 p.m.