Triple
T28037309
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shaun Pye |
E708443
|
entity |
| Predicate | basedOnPersonalExperience |
P75036
|
FINISHED |
| Object | There She Goes |
—
|
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: There She Goes | Statement: [Shaun Pye, basedOnPersonalExperience, There She Goes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basedOnPersonalExperience Context triple: [Shaun Pye, basedOnPersonalExperience, There She Goes]
-
A.
basedOnExperience
chosen
Indicates that something is determined, chosen, or formed according to prior experience or experiential knowledge.
-
B.
gaveFirsthandExperienceOf
Indicates that one entity directly provided another entity with personal, firsthand experience of something, rather than secondhand or indirect knowledge.
-
C.
mayExperience
Indicates that an entity is capable of undergoing, feeling, or being subject to a particular event, state, or condition.
-
D.
primaryExperience
Indicates that one entity is the main or most significant experience associated with another entity, as opposed to secondary or supporting experiences.
-
E.
experiences
Indicates that an entity undergoes, feels, or is affected by a particular event, state, or condition.
- 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_69ef9b6cf538819094a633ffa67afec1 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f7b2f3a104819098ddd8909eaf596c |
completed | May 3, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f7b1b8a9fc8190a1279e67a2d12707 |
completed | May 3, 2026, 8:36 p.m. |
Created at: April 27, 2026, 8:22 p.m.