Triple
T27981578
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Big Daddy Splash |
E706637
|
entity |
| Predicate | typicalMatchRole |
P85537
|
FINISHED |
| Object | match-ending move |
—
|
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: match-ending move | Statement: [Big Daddy Splash, typicalMatchRole, match-ending move]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalMatchRole Context triple: [Big Daddy Splash, typicalMatchRole, match-ending move]
-
A.
typicalAdditionalRole
Indicates that an entity commonly or characteristically holds an extra role or function in addition to its primary one.
-
B.
typicalRole
Indicates that one entity serves as the usual, characteristic, or commonly expected role or function of another entity.
-
C.
typicalMatchType
Indicates the usual or most common type of match or pairing that characterizes how two entities are related or aligned.
-
D.
roleInRecordMatch
Indicates the specific function or position an entity holds within a particular record-matching relationship or comparison.
-
E.
typicalPerformerRoleType
chosen
Indicates the usual or characteristic role type that a performer commonly plays or is associated with in their performances.
- 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_69ef96b8b8d88190bad5e4ae966bf14e |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_6a004b6ad4248190b402a0d01b0ebf83 |
completed | May 10, 2026, 9:10 a.m. |
| PD | Predicate disambiguation | batch_6a004ae736b881908a0efed8f63f982e |
completed | May 10, 2026, 9:07 a.m. |
Created at: April 27, 2026, 7:44 p.m.