Triple
T512815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gerald Ford |
E10642
|
entity |
| Predicate | congressionalServiceStart |
P15402
|
FINISHED |
| Object | 1949 |
—
|
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: 1949 | Statement: [Gerald Ford, congressionalServiceStart, 1949]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: congressionalServiceStart Context triple: [Gerald Ford, congressionalServiceStart, 1949]
-
A.
parliamentaryServiceStart
Indicates the date or point in time when an entity’s service in a parliamentary role or body begins.
-
B.
legislativeActivity
Indicates involvement in creating, debating, amending, or passing laws or related legislative measures.
-
C.
coLegislatureWith
Indicates that two legislative bodies share lawmaking authority within the same political system or jurisdiction.
-
D.
representedInCongressBy
Indicates that one entity serves as the official congressional representative (e.g., legislator) for another entity (such as a person, group, or geographic area).
-
E.
currentRepresentativeChamber
Indicates that an entity currently serves as a representative in a specific legislative chamber.
- 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_69a2e84a0d08819087e01863fcd9abf1 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f232fa688190b08a2fe3f22c7a6e |
completed | Feb. 28, 2026, 1:48 p.m. |
| PD | Predicate disambiguation | batch_69a2f013c05481909e6dc87e7b20ebd8 |
completed | Feb. 28, 2026, 1:39 p.m. |
| PDg | Predicate description generation | batch_69a2f23214248190aa5fe1138f0f5a58 |
completed | Feb. 28, 2026, 1:48 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.