Triple
T28773992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aspar |
E726484
|
entity |
| Predicate | influencedAppointmentOf |
P178039
|
FINISHED |
| Object | Marcian |
—
|
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: Marcian | Statement: [Aspar, influencedAppointmentOf, Marcian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: influencedAppointmentOf Context triple: [Aspar, influencedAppointmentOf, Marcian]
-
A.
administrativeInfluenceOn
Indicates that one entity has the authority or capacity to affect, direct, or shape the administration, management, or governance of another entity.
-
B.
influencedIn
Indicates that one entity had an effect on or shaped another entity within a specific context, domain, or setting.
-
C.
influenceOf
Indicates that one entity affects, shapes, or alters the state, behavior, or properties of another entity.
-
D.
appointedIn
Indicates that an entity is formally assigned or designated to a role, position, or office within a specific context, organization, or jurisdiction.
-
E.
appointedBy
Indicates that one entity has been formally selected or assigned to a position, role, or office by another entity.
- 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_69f03199997c8190b6ae43fb19312443 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f707f7959881908f037f0d6b1d0c36 |
completed | May 3, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69f700fc274c8190a128593dc7c7abd0 |
completed | May 3, 2026, 8:02 a.m. |
| PDg | Predicate description generation | batch_69f707f380388190954b79d52a321921 |
completed | May 3, 2026, 8:31 a.m. |
Created at: April 28, 2026, 6:17 a.m.