Triple
T38585982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aedelas Blackmoore |
E932346
|
entity |
| Predicate | trainedAsGladiator |
P22559
|
FINISHED |
| Object | Thrall |
—
|
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: Thrall | Statement: [Aedelas Blackmoore, trainedAsGladiator, Thrall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trainedAsGladiator Context triple: [Aedelas Blackmoore, trainedAsGladiator, Thrall]
-
A.
trainedAsWrestlerIn
Indicates that one entity received wrestling training in a specific place, organization, or context associated with the other entity.
-
B.
trainedAs
chosen
Indicates that one entity has received education or instruction to perform the role, profession, or function represented by another entity.
-
C.
physicallyConditionedAs
Indicates that one entity has been brought into or exists in a particular physical state or condition as specified by another entity or descriptor.
-
D.
roleInRome
Indicates that an entity holds or held a specific role, position, or function within the context of Rome or Roman society.
-
E.
combatProven
Indicates that something has been tested and demonstrated effective performance in actual combat or real-world conflict situations.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdaa36f90819093f8661969990c7d |
completed | May 7, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fefc588190b063d7ea1ec87b07 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:32 p.m.