Triple
T31773963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michael E. Fossum |
E811015
|
entity |
| Predicate | totalEVAExperience |
P102959
|
FINISHED |
| Object | 48 hours 32 minutes |
—
|
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: 48 hours 32 minutes | Statement: [Michael E. Fossum, totalEVAExperience, 48 hours 32 minutes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: totalEVAExperience Context triple: [Michael E. Fossum, totalEVAExperience, 48 hours 32 minutes]
-
A.
providesExperienceOf
Indicates that one entity enables or delivers the experience of another entity to someone or something.
-
B.
experienceDuration
chosen
Indicates the length of time over which an entity undergoes or has undergone a particular experience or event.
-
C.
typeOfExperience
Indicates that one entity specifies the category or nature of an experience associated with another entity.
-
D.
settingOfExperience
Indicates that a particular context, environment, or situation serves as the backdrop or circumstances in which an experience occurs.
-
E.
usedExperienceIn
Indicates that an entity applied or leveraged a particular experience or expertise in performing an action or achieving a result.
- 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_69f348e544a48190ab6e700b05f6438c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f757898fe48190b124dc7301672623 |
completed | May 3, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69f754c484348190948d2a04ff228fb1 |
completed | May 3, 2026, 1:59 p.m. |
Created at: April 30, 2026, 11:34 p.m.