Triple
T32881334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frank Richards |
E841071
|
entity |
| Predicate | describedEvents |
P115640
|
FINISHED |
| Object | Western Front in World War I |
—
|
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: Western Front in World War I | Statement: [Frank Richards, describedEvents, Western Front in World War I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: describedEvents Context triple: [Frank Richards, describedEvents, Western Front in World War I]
-
A.
basedOnEventsDescribedIn
Indicates that something is derived from, inspired by, or constructed using the events described in another source.
-
B.
eventDescription
Indicates that a textual summary or explanation is provided describing what happens in the event.
-
C.
observedEvent
Indicates that an entity has perceived, detected, or recorded the occurrence of a particular event.
-
D.
historicalEventsDescribed
chosen
Indicates that one entity (such as a document, text, or account) describes or recounts the historical events associated with another entity.
-
E.
recordsEventsVia
Indicates that one entity captures or logs events through the mechanism, system, or medium provided by another entity.
- 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_69f349446e288190a70c05bcc4d81172 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fbaebc8f2c8190b94f1b4a3ec92e8c |
completed | May 6, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69fbadf1e6008190a71bbd196ba06844 |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 1, 2026, 1:18 a.m.