Triple
T29015793
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Allectus |
E737302
|
entity |
| Predicate | allegianceBeforeUsurpation |
P116242
|
FINISHED |
| Object | Carausius |
—
|
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: Carausius | Statement: [Allectus, allegianceBeforeUsurpation, Carausius]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allegianceBeforeUsurpation Context triple: [Allectus, allegianceBeforeUsurpation, Carausius]
-
A.
allegianceBeforeRule
chosen
Indicates that one party’s allegiance or loyalty to another existed prior to the latter’s assumption of rule or authority.
-
B.
hadAllegiance
Indicates that an entity was loyally committed or formally bound in support or service to another entity, such as a person, group, or cause.
-
C.
allegiance
Indicates a relationship where one entity is loyal, committed, or obligated in support or service to another entity.
-
D.
changeOfAllegiance
Indicates a shift in loyalty or support from one party, group, or cause to another.
-
E.
namedForAllegiance
Indicates that an entity is named in reference to, or in honor of, a particular allegiance, affiliation, or loyalty.
- 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_69f077ee19f881909af48f9cab00a2e5 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f969b4cc8190afb473a2d8b110bc |
completed | May 3, 2026, 7:29 a.m. |
Created at: April 28, 2026, 9:45 a.m.