Triple
T36052626
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | James Fogle |
E1042853
|
entity |
| Predicate | workBasedOnExperience |
P148321
|
FINISHED |
| Object | "Drugstore Cowboy" |
—
|
NE NERFINISHED |
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: "Drugstore Cowboy" | Statement: [James Fogle, workBasedOnExperience, "Drugstore Cowboy"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workBasedOnExperience Context triple: [James Fogle, workBasedOnExperience, "Drugstore Cowboy"]
-
A.
basedOnExperience
Indicates that something is determined, chosen, or formed according to prior experience or experiential knowledge.
-
B.
usedExperienceIn
chosen
Indicates that an entity applied or leveraged a particular experience or expertise in performing an action or achieving a result.
-
C.
experienceType
Indicates the specific kind or category of experience associated with an entity or event.
-
D.
typeOfExperience
Indicates that one entity specifies the category or nature of an experience associated with another entity.
-
E.
hasExperienceOf
Indicates that one entity has undergone, encountered, or lived through a particular event, situation, or activity associated with another entity.
- 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_69f76e2e41f8819091f9fb0536920fec |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7b2c771108190adeec151daad5dab |
completed | May 3, 2026, 8:40 p.m. |
| PD | Predicate disambiguation | batch_69f7b1bad2e88190963ab4ee5d4f2038 |
completed | May 3, 2026, 8:36 p.m. |
Created at: May 3, 2026, 4:07 p.m.