Triple
T35208043
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Becky Lynch |
E1016592
|
entity |
| Predicate | hasEntranceThemeAssociatedWith |
P184146
|
FINISHED |
| Object | The Man |
—
|
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: The Man | Statement: [Becky Lynch, hasEntranceThemeAssociatedWith, The Man]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEntranceThemeAssociatedWith Context triple: [Becky Lynch, hasEntranceThemeAssociatedWith, The Man]
-
A.
isEntranceThemeOf
chosen
Indicates that a particular musical piece or motif serves as the entrance theme associated with a specific entity (such as a character, performer, or event).
-
B.
entranceTheme
Indicates the music or theme that plays when an entity makes their entrance or initial appearance.
-
C.
hasEntrancesIn
Indicates that an entity has one or more entrances located within or opening into another specified entity or area.
-
D.
hasEntrance
Indicates that one entity possesses or provides an entry point or access way to another entity or space.
-
E.
hasEntranceOn
Indicates that one entity’s entrance or access point is located on or faces a specified side, boundary, or feature of 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_69f76ddf549c8190869d0af076fd2c28 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd5f29b1988190877764ef2a399c7f |
completed | May 8, 2026, 3:57 a.m. |
| PD | Predicate disambiguation | batch_69fd5e30194c819085b5ce586122ab37 |
completed | May 8, 2026, 3:53 a.m. |
Created at: May 3, 2026, 4:02 p.m.