Triple
T33451571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earl of Cardigan |
E856654
|
entity |
| Predicate | historicallyLinkedEvent |
P16345
|
FINISHED |
| Object | Charge of the Light Brigade |
—
|
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: Charge of the Light Brigade | Statement: [Earl of Cardigan, historicallyLinkedEvent, Charge of the Light Brigade]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicallyLinkedEvent Context triple: [Earl of Cardigan, historicallyLinkedEvent, Charge of the Light Brigade]
-
A.
historicallyLinked
chosen
Indicates that two entities are connected through a shared or related historical event, period, or development.
-
B.
hasHistoricalEvent
Indicates that a historical event occurred in, is associated with, or is relevant to a particular entity.
-
C.
associatedEpicEvent
Indicates that one entity is linked or connected to a particular epic event in a relevant or meaningful way.
-
D.
hasNearbyHistoricalEvent
Indicates that a given entity is located close to the site where a specific historical event occurred.
-
E.
closelyAssociatedEvent
Indicates that one event is strongly related to, connected with, or occurs in close conjunction with another event.
- 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_69f3497281a08190b4705de0b5f26ba7 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a00037bf4148190a58593d30efdd3f8 |
completed | May 10, 2026, 4:03 a.m. |
| PD | Predicate disambiguation | batch_6a0000b7af608190b718fc4111bcdad8 |
completed | May 10, 2026, 3:51 a.m. |
Created at: May 1, 2026, 1:37 a.m.