Triple
T226209
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Senate Majority Leader |
E4318
|
entity |
| Predicate | selectedBy |
P381
|
FINISHED |
| Object | Senate majority party senators |
—
|
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: Senate majority party senators | Statement: [Senate Majority Leader, selectedBy, Senate majority party senators]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: selectedBy Context triple: [Senate Majority Leader, selectedBy, Senate majority party senators]
-
A.
selectionMadeBy
chosen
Indicates that a particular choice or selection was performed or decided by a specific agent or entity.
-
B.
selectionReason
Indicates the reason or justification for choosing or selecting one entity over alternatives.
-
C.
selectionMethodChangedBy
Indicates that one entity causes or is responsible for a change in the method or criteria used to make a selection.
-
D.
selectionCriteria
Indicates the conditions or rules used to choose certain entities from a larger set.
-
E.
selectionProcess
Indicates the procedure or set of steps by which one or more options are evaluated and chosen from a larger set of candidates.
- 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_69a257363ffc81909757bde7ab3404da |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25dec53ac8190912f3d79576131fa |
completed | Feb. 28, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69a25b5739dc8190bad8bfa330ce0499 |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.