Triple
T28793484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Macrobius |
E727021
|
entity |
| Predicate | statusOfWorksInMiddleAges |
P119731
|
FINISHED |
| Object | highly read |
—
|
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: highly read | Statement: [Macrobius, statusOfWorksInMiddleAges, highly read]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusOfWorksInMiddleAges Context triple: [Macrobius, statusOfWorksInMiddleAges, highly read]
-
A.
functionDuringMiddleAges
Indicates that the function, role, or activity occurred specifically during the Middle Ages period.
-
B.
medievalStatus
Indicates the social, legal, or hierarchical standing an entity holds within a medieval societal structure.
-
C.
medievalSignificance
chosen
Indicates that something holds notable importance, influence, or relevance within the context of the medieval period.
-
D.
medievalState
Indicates that an entity functioned as a state or political unit during the medieval historical period.
-
E.
statusIn15thCentury
Indicates the status, condition, or standing that an entity had specifically during the 15th century.
- 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_69f0319b7c44819085736bcc256185e6 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69fd19f791f48190bbb6f6047f9ddc59 |
completed | May 7, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69fd0df365948190bc9bfc7ffd46acd8 |
completed | May 7, 2026, 10:10 p.m. |
Created at: April 28, 2026, 6:24 a.m.