Triple
T27879214
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Impact World Championship |
E705040
|
entity |
| Predicate | hasScriptedRules |
P108535
|
FINISHED |
| Object | standard professional wrestling rules |
—
|
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: standard professional wrestling rules | Statement: [Impact World Championship, hasScriptedRules, standard professional wrestling rules]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasScriptedRules Context triple: [Impact World Championship, hasScriptedRules, standard professional wrestling rules]
-
A.
hasScriptedNature
chosen
Indicates that something is predetermined or follows a written or planned script rather than occurring spontaneously.
-
B.
hasScriptRegulator
Indicates that an entity has an associated mechanism or component that controls or governs its script or scripting behavior.
-
C.
containsScript
Indicates that one entity includes or embeds the script of another entity within it.
-
D.
canBeScripted
Indicates that the action or behavior can be defined, controlled, or automated through a script or scripting mechanism.
-
E.
hasScriptBy
Indicates that one entity has its script authored, written, or created by 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_69ef84111bb4819084298f994b31c62f |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f6d6a6b04c8190bee4cf9c00665ef7 |
completed | May 3, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f6d26ceb08819091c71c001e954936 |
completed | May 3, 2026, 4:43 a.m. |
Created at: April 27, 2026, 6:29 p.m.