Triple
T38572052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Benno (Siegfried’s friend) |
E929300
|
entity |
| Predicate | hasActivityInStory |
P19746
|
FINISHED |
| Object | hunting |
—
|
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: hunting | Statement: [Benno (Siegfried’s friend), hasActivityInStory, hunting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasActivityInStory Context triple: [Benno (Siegfried’s friend), hasActivityInStory, hunting]
-
A.
hasTimeInStory
Indicates that a story element, event, or entity occurs or is present during a specific time or time interval within the narrative.
-
B.
hasActivityIn
chosen
Indicates that an entity engages in or performs a particular activity within a specified context, location, or domain.
-
C.
hasPublicActivity
Indicates that an entity engages in actions or behaviors that are visible or accessible to the general public.
-
D.
hasManagerInStory
Indicates that one entity serves as the manager of another entity within the context of a specific story or narrative.
-
E.
hasPopularActivity
Indicates that an entity is associated with an activity that is widely favored, frequently engaged in, or well-liked by many people.
- 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_69f76ebd2248819083978362d81fa35e |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd592e48cc81909d754cc6c4bd99ae |
completed | May 8, 2026, 3:31 a.m. |
| PD | Predicate disambiguation | batch_69fd58b7f9b881909dc099b28d567784 |
completed | May 8, 2026, 3:30 a.m. |
Created at: May 3, 2026, 4:32 p.m.