Triple
T25803822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A. Piatt Andrew |
E649909
|
entity |
| Predicate | worked at |
P17879
|
FINISHED |
| Object | U.S. Department of the Treasury |
—
|
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: U.S. Department of the Treasury | Statement: [A. Piatt Andrew, worked at, U.S. Department of the Treasury]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worked at Context triple: [A. Piatt Andrew, worked at, U.S. Department of the Treasury]
-
A.
workedAs
Indicates that an entity held a particular job, role, or position, performing work in that capacity.
-
B.
workedFrom
Indicates that an entity was employed or actively engaged in work starting from a specified point in time.
-
C.
workedPrimarilyOn
Indicates that an entity devoted the majority of its work, effort, or activity to a particular project, field, or subject.
-
D.
hasWorkedIn
chosen
Indicates that a person has been employed or has performed work within a particular organization, location, or domain for some period of time.
-
E.
workedUnder
Indicates that one entity was hierarchically subordinate to and performed work under the supervision or authority of 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_69e7ab34f8c8819099f6c4dabdabf129 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6135293908190809e255bf6334760 |
completed | May 2, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_69f611a72780819082f44e66ca2c6ac9 |
completed | May 2, 2026, 3 p.m. |
Created at: April 22, 2026, 6:44 a.m.