Triple
T34498961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | court of Honorius |
E885694
|
entity |
| Predicate | influentialCourtier |
P154906
|
FINISHED |
| Object | Olympius |
—
|
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: Olympius | Statement: [court of Honorius, influentialCourtier, Olympius]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: influentialCourtier Context triple: [court of Honorius, influentialCourtier, Olympius]
-
A.
notableCourtier
chosen
Indicates that a person served as a courtier and is recognized as particularly prominent or noteworthy in that role.
-
B.
influentialAs
Indicates that one entity has at least as much influence or impact as another entity.
-
C.
influentialFrom
Indicates that one entity has exerted influence on another, contributing to or shaping the latter’s ideas, behavior, or development.
-
D.
aristocraticActivity
Indicates activities, behaviors, or pursuits that are characteristic of or associated with aristocrats or the aristocracy.
-
E.
aristocraticNetwork
Indicates a social or familial connection among members of the aristocracy, typically involving shared status, influence, or lineage.
- 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_69f349cafcec8190997b45b3fdc16c27 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd2a215d6c8190a1a428ccaee603f1 |
completed | May 8, 2026, 12:11 a.m. |
| PD | Predicate disambiguation | batch_69fd28ef19688190bb8370f2812a43e7 |
completed | May 8, 2026, 12:06 a.m. |
Created at: May 1, 2026, 2:01 a.m.