Triple
T34641331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Essex Regiment |
E889564
|
entity |
| Predicate | promotionOf |
P147263
|
FINISHED |
| Object | Richard Sharpe |
—
|
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: Richard Sharpe | Statement: [South Essex Regiment, promotionOf, Richard Sharpe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: promotionOf Context triple: [South Essex Regiment, promotionOf, Richard Sharpe]
-
A.
promotionFor
Indicates that one entity serves as a promotional activity, material, or campaign intended to advertise, support, or increase the visibility of another entity.
-
B.
promotionBy
chosen
Indicates that one entity advances, elevates, or publicizes another entity, typically by increasing its status, visibility, or level.
-
C.
promotionIn
Indicates that an entity is being advanced, elevated, or upgraded within a specified context, organization, or domain.
-
D.
promotionTo
Indicates that one entity is elevated or advanced to a higher rank, position, or status relative to another entity or context.
-
E.
promotionFrom
Indicates that an entity has been elevated in position, rank, or status from a specified prior role or level.
- 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_69f349d724848190b63ad3407e0006d9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f760a35b988190904e6267553ad2fe |
completed | May 3, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69f75eb3d6f081908c933474eb359e3d |
completed | May 3, 2026, 2:41 p.m. |
Created at: May 1, 2026, 2:04 a.m.