Triple
T1485585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | William Howard Russell |
E29455
|
entity |
| Predicate | reportedFrom |
P9386
|
FINISHED |
| Object | Crimean War battlefields |
—
|
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: Crimean War battlefields | Statement: [William Howard Russell, reportedFrom, Crimean War battlefields]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reportedFrom Context triple: [William Howard Russell, reportedFrom, Crimean War battlefields]
-
A.
transmittedFrom
Indicates that something (such as information, a signal, or a disease) has been passed or conveyed from one source entity to another.
-
B.
reportedOn
chosen
Indicates that one entity has provided an account, description, or coverage of another entity, typically as news, documentation, or an official report.
-
C.
isFrom
Indicates that one entity originates, comes, or has been sent from another entity or source.
-
D.
proclaimedFrom
Indicates that something was formally announced or declared originating from a particular source, place, or authority.
-
E.
attestedFrom
Indicates the earliest point in time or source from which something is documented, recorded, or evidenced as existing or in use.
- 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_69a498da82e08190ba833330d05f380f |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c6a1d8448190b3c90bb82fd806fe |
completed | March 1, 2026, 11:07 p.m. |
| PD | Predicate disambiguation | batch_69a4c486eacc81909c272f9bdf50a7c3 |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8:12 p.m.