Triple
T38136903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Endicott Board |
E952373
|
entity |
| Predicate | positionHeldByChair |
P201699
|
FINISHED |
| Object | United States Secretary of War |
—
|
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: United States Secretary of War | Statement: [Endicott Board, positionHeldByChair, United States Secretary of War]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionHeldByChair Context triple: [Endicott Board, positionHeldByChair, United States Secretary of War]
-
A.
chairHeldBy
Indicates that a chair is currently being physically held or supported by a particular entity.
-
B.
chairHolderField
Indicates that a field specifies or identifies the holder (person or entity) of a chair position.
-
C.
chairHolderStatus
Indicates the status or condition of an entity in relation to holding a specific chair or official position.
-
D.
permanentChair
Indicates that an entity holds an ongoing, officially designated chair or leadership position that is not intended to be temporary or rotating.
-
E.
chairHolderType
Indicates the specific category or role of the person or entity that holds a particular chair or position.
- F. None of above. chosen
Provenance (4 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_69f76f09a7148190a4b91c0bacdc127a |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a001540d4f881908a4688881875e774 |
completed | May 10, 2026, 5:18 a.m. |
| PD | Predicate disambiguation | batch_6a0014a8cdd88190a67a90a2df2c5e18 |
completed | May 10, 2026, 5:16 a.m. |
| PDg | Predicate description generation | batch_6a00153fea20819086ff5888bf725d05 |
completed | May 10, 2026, 5:18 a.m. |
Created at: May 3, 2026, 4:21 p.m.