Triple
T1955341
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stratfield Saye House |
E42254
|
entity |
| Predicate | grantReason |
P18220
|
FINISHED |
| Object | reward for victory at the Battle of Waterloo |
—
|
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: reward for victory at the Battle of Waterloo | Statement: [Stratfield Saye House, grantReason, reward for victory at the Battle of Waterloo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: grantReason Context triple: [Stratfield Saye House, grantReason, reward for victory at the Battle of Waterloo]
-
A.
reasonForGrant
chosen
Indicates the justification, purpose, or cause for which a grant is awarded or provided.
-
B.
statedReason
Indicates that one entity expresses or provides another entity as the explanation, justification, or motive for an action, event, or claim.
-
C.
designationReason
Indicates the reason or justification for assigning a particular designation or status to an entity.
-
D.
reasonWritten
Indicates that one entity is the reason or motivation for which another entity was written or authored.
-
E.
suspensionReason
Indicates the reason or cause for which an entity has been suspended from a status, activity, or service.
- 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_69a8870eea088190a38781990812a9bc |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb353aa8c81909810347f9981a02f |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abaff3eda88190b643994cb4dfb8df |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:36 p.m.