Triple
T29186558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rasa (aesthetic flavor) |
E739882
|
entity |
| Predicate | experiencedBy |
P106748
|
FINISHED |
| Object | spectator |
—
|
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: spectator | Statement: [Rasa (aesthetic flavor), experiencedBy, spectator]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: experiencedBy Context triple: [Rasa (aesthetic flavor), experiencedBy, spectator]
-
A.
gaveFirsthandExperienceOf
Indicates that one entity directly provided another entity with personal, firsthand experience of something, rather than secondhand or indirect knowledge.
-
B.
experiencedByCharacter
chosen
Indicates that a particular event, situation, or emotion is undergone or lived through by a specific character.
-
C.
mayExperience
Indicates that an entity is capable of undergoing, feeling, or being subject to a particular event, state, or condition.
-
D.
providesExperienceOf
Indicates that one entity enables or delivers the experience of another entity to someone or something.
-
E.
allegedlyExperienced
Indicates that an entity is claimed or reported to have undergone or had a particular experience, without asserting that the experience actually occurred.
- 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_69f07cb74c2c8190ad396487fcb4fde6 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f66d7765208190b87b1cc6d96a151c |
completed | May 2, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69f66abfdaf08190a55f14c70be6fd4d |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 28, 2026, noon