Triple
T25803830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A. Piatt Andrew |
E649909
|
entity |
| Predicate | notable office |
P20021
|
FINISHED |
| Object | Director of the U.S. Mint (acting) |
—
|
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: Director of the U.S. Mint (acting) | Statement: [A. Piatt Andrew, notable office, Director of the U.S. Mint (acting)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notable office Context triple: [A. Piatt Andrew, notable office, Director of the U.S. Mint (acting)]
-
A.
notableOfficeLevel
Indicates that an entity holds or is associated with a notable office or position at a specified hierarchical level.
-
B.
notableFormerOfficeHolderRole
Indicates that an entity previously held a particular official position or role that is considered notable.
-
C.
notableOfficer
Indicates that an entity has served as a significant or distinguished officer of another entity, such as an organization, institution, or group.
-
D.
notableOfficePeriod
Indicates that an entity held a particular office or position during a specified time period.
-
E.
notableTitleHeld
chosen
Indicates that an entity has held a distinguished or noteworthy title, rank, or official position.
- 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_69fda94697c4819081291967202248be |
completed | May 8, 2026, 9:13 a.m. |
| PD | Predicate disambiguation | batch_69fda5973fcc8190a57daef31fb70a49 |
completed | May 8, 2026, 8:57 a.m. |
Created at: April 22, 2026, 6:44 a.m.