Triple
T20136277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | James J. Andrews |
E491032
|
entity |
| Predicate | notableParticipantsInRaid |
P6467
|
FINISHED |
| Object | Union volunteer soldiers |
—
|
LITERAL FINISHED |
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: Union volunteer soldiers | Statement: [James J. Andrews, notableParticipantsInRaid, Union volunteer soldiers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableParticipantsInRaid Context triple: [James J. Andrews, notableParticipantsInRaid, Union volunteer soldiers]
-
A.
associatedRaid
Indicates a relationship where one entity is linked to or involved with a particular raid event or operation.
-
B.
finalRaidEncounter
Indicates that an encounter represents the ultimate or concluding boss fight or challenge within a raid.
-
C.
notableBoss
Indicates that one entity is a boss or superior of another in a way that is particularly prominent, distinguished, or noteworthy.
-
D.
raidingPattern
Indicates a recurring or characteristic way in which raids are planned, organized, or carried out between entities.
-
E.
notableParticipant
chosen
Indicates that an entity plays a significant or distinguished role as a participant in an event, activity, or context.
- 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_69da62651a0c8190a3e05e95e056a66b |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e66767ba3881909c2bcb74a986bd29 |
completed | April 20, 2026, 5:50 p.m. |
| PD | Predicate disambiguation | batch_69e54cfb0d0081908e789b9b57e96668 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 11:32 p.m.