Triple
T30925612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Annoyance Theatre |
E787845
|
entity |
| Predicate | hasTrainingPhilosophy |
P49601
|
FINISHED |
| Object | follow the fear |
—
|
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: follow the fear | Statement: [Annoyance Theatre, hasTrainingPhilosophy, follow the fear]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTrainingPhilosophy Context triple: [Annoyance Theatre, hasTrainingPhilosophy, follow the fear]
-
A.
hasTrainingTrack
Indicates that an entity is associated with or assigned to a specific training track or program.
-
B.
hasPhilosophyAbout
chosen
Indicates that one entity holds, develops, or expresses a philosophical view, theory, or stance concerning another entity or subject.
-
C.
hasTrainingPitch
Indicates that an entity possesses or is associated with a specific training pitch or practice field.
-
D.
hasTrainingFor
Indicates that an entity has received or possesses training that prepares it for performing a specific task, role, or function.
-
E.
hasTrainingComplex
Indicates that an entity possesses or is associated with a dedicated facility or complex used for training activities.
- 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_69f224bfaca88190b9d0dfcc86297fe9 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fea5e828cc8190a9b755a645dc56d2 |
completed | May 9, 2026, 3:11 a.m. |
| PD | Predicate disambiguation | batch_69fea36443f08190b2aced9b4a0525fd |
completed | May 9, 2026, 3 a.m. |
Created at: April 29, 2026, 8:51 p.m.