Triple
T18778571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maxine Waters |
E459192
|
entity |
| Predicate | notable phrase |
P53846
|
FINISHED |
| Object | "reclaiming my time" |
—
|
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: "reclaiming my time" | Statement: [Maxine Waters, notable phrase, "reclaiming my time"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notable phrase Context triple: [Maxine Waters, notable phrase, "reclaiming my time"]
-
A.
hasNotablePhrase
chosen
Indicates that an entity is associated with a specific phrase or expression that is considered notable or characteristic of it.
-
B.
notableExpression
Indicates that an entity is known for or characterized by a particular expression, gesture, or manner of expression.
-
C.
notableInterpretation
Indicates that an entity is a significant or widely recognized interpretation, rendition, or version of another work, concept, or subject.
-
D.
notableFor
Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or role.
-
E.
notableUse
Indicates that something is prominently or famously used by a particular entity, context, or for a specific purpose.
- 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_69d8d396f54c8190ba49db31e8743842 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5933d2d048190a42480edc70bf086 |
completed | April 20, 2026, 2:45 a.m. |
| PD | Predicate disambiguation | batch_69e48d1126e4819099607837ed5aadca |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:52 a.m.