Triple
T347188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nathanael Greene |
E6966
|
entity |
| Predicate | appointedToPosition |
P8660
|
FINISHED |
| Object | Commander of the Southern Department |
—
|
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: Commander of the Southern Department | Statement: [Nathanael Greene, appointedToPosition, Commander of the Southern Department]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appointedToPosition Context triple: [Nathanael Greene, appointedToPosition, Commander of the Southern Department]
-
A.
appointed
chosen
Indicates that one entity formally assigns another entity to a position, role, or responsibility.
-
B.
appointedAfter
Indicates that one entity was appointed to a position or role at a later time than another entity.
-
C.
appointedAs
Indicates that one entity is formally assigned or designated to hold a specific role, position, or title in relation to another entity.
-
D.
appointedBy
Indicates that one entity has been formally selected or assigned to a position, role, or office by another entity.
-
E.
appointedByOffice
Indicates that an entity attains its position or role through a formal appointment made by a specific office or official authority.
- 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_69a2e7951ba08190960e90823b5078f3 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2eb1a37c08190b1380f6bf8513a37 |
completed | Feb. 28, 2026, 1:18 p.m. |
| PD | Predicate disambiguation | batch_69a2e95451a4819090f4e4fb9b21a493 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.