Triple
T24327905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lucilla (Gladiator) |
E613151
|
entity |
| Predicate | conflictedLoyaltyWith |
P32882
|
FINISHED |
| Object | Commodus (Gladiator) |
—
|
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: Commodus (Gladiator) | Statement: [Lucilla (Gladiator), conflictedLoyaltyWith, Commodus (Gladiator)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conflictedLoyaltyWith Context triple: [Lucilla (Gladiator), conflictedLoyaltyWith, Commodus (Gladiator)]
-
A.
loyaltyConflict
chosen
Indicates a situation where an entity’s loyalties to different people, groups, or principles are in tension or opposition, creating a conflict in choosing whom or what to support.
-
B.
allegiance
Indicates a relationship where one entity is loyal, committed, or obligated in support or service to another entity.
-
C.
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.
-
D.
partnerInConflictWith
Indicates that two entities are engaged as opposing partners or sides within the same conflict or dispute.
-
E.
facedConflictOver
Indicates that two or more entities experienced opposition, dispute, or tension concerning a particular issue, resource, or situation.
- 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_69e2d7db6d5c819091194918157a7c1f |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f292eebf7081908ef50ef331ff88aa |
completed | April 29, 2026, 11:23 p.m. |
| PD | Predicate disambiguation | batch_69f287ad30048190b3ad3613486f277f |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 1:54 a.m.