Triple
T5751
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | President of the United States |
E112
|
entity |
| Predicate | termLimit |
P99
|
FINISHED |
| Object | two elected terms |
—
|
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: two elected terms | Statement: [President of the United States, termLimit, two elected terms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: termLimit Context triple: [President of the United States, termLimit, two elected terms]
-
A.
termCountAsPresident
Indicates the number of terms an individual has served in the role of president.
-
B.
legislature
Indicates that an entity serves as, or is part of, a law-making body or assembly responsible for creating or amending laws for a political unit.
-
C.
hasLimitation
chosen
Indicates that an entity is subject to a constraint, restriction, or boundary that limits its scope, capability, or applicability.
-
D.
hasElectoralVotes
Indicates that a political entity (such as a state or district) possesses a specified number of votes in an electoral system used to choose an officeholder.
-
E.
positionHeld
Indicates that an entity occupies or has occupied a specific role, job, office, or position within an organization or context.
- 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_69a238d6b47881909e68288aed2fd858 |
completed | Feb. 28, 2026, 12:37 a.m. |
| NER | Named-entity recognition | batch_69a23ae754fc8190812506055ce94672 |
completed | Feb. 28, 2026, 12:46 a.m. |
| PD | Predicate disambiguation | batch_69a239997f888190bf941b74fbc9c15f |
completed | Feb. 28, 2026, 12:40 a.m. |
Created at: Feb. 28, 2026, 12:40 a.m.