Triple
T1510984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | William H. Winder |
E32010
|
entity |
| Predicate | afterWarActivity |
P13560
|
FINISHED |
| Object | returned to legal practice |
—
|
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: returned to legal practice | Statement: [William H. Winder, afterWarActivity, returned to legal practice]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: afterWarActivity Context triple: [William H. Winder, afterWarActivity, returned to legal practice]
-
A.
postwarActivity
chosen
Indicates activities, roles, or developments associated with an entity specifically in the period following a war or major conflict.
-
B.
usedAfterWar
Indicates that an entity came into use only after a specific war or conflict had ended.
-
C.
postwarOutcome
Indicates the result or consequences that follow for a party or situation after a war has ended.
-
D.
functionAfterCivilWar
Indicates that one entity serves or operates in a particular function, role, or capacity following the end of a civil war.
-
E.
concludedWar
Indicates that a war or armed conflict between entities has come to an end, typically through victory, surrender, or formal agreement.
- 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_69a885e8caf88190a5fbb6159ce87786 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a9396e16408190b5e7b0ac43376d81 |
completed | March 5, 2026, 8:06 a.m. |
| PD | Predicate disambiguation | batch_69a907aa67cc81909f00135365447399 |
completed | March 5, 2026, 4:33 a.m. |
Created at: March 4, 2026, 7:26 p.m.