Triple
T4060621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michael Phelps |
E86200
|
entity |
| Predicate | focusOfFoundation |
P31
|
FINISHED |
| Object | promoting water safety |
—
|
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: promoting water safety | Statement: [Michael Phelps, focusOfFoundation, promoting water safety]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: focusOfFoundation Context triple: [Michael Phelps, focusOfFoundation, promoting water safety]
-
A.
purposeOfFoundation
Indicates the reason or intended goal for which an organization, institution, or entity was originally established.
-
B.
focusType
Indicates the specific kind or category of focus or attention that is being applied to or associated with an entity or interaction.
-
C.
claimsFoundationBy
Indicates that one entity asserts or declares that another entity serves as its basis, origin, or underlying foundation.
-
D.
focusesOn
chosen
Indicates that one entity directs its attention, effort, or primary activity toward another entity or specific subject.
-
E.
foundedFor
Indicates that an entity was established or created specifically to serve, support, or benefit another entity or 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_69aed93c69208190a4efac0efe3cd69b |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefd0bdea48190805a79515ee92709 |
completed | March 9, 2026, 5:02 p.m. |
| PD | Predicate disambiguation | batch_69aef90438908190a005b08ba271eacf |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:38 p.m.