Triple
T10910409
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Twenty20 International cricket |
E257681
|
entity |
| Predicate | formatGoal |
P32840
|
FINISHED |
| Object | increase spectator appeal |
—
|
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: increase spectator appeal | Statement: [Twenty20 International cricket, formatGoal, increase spectator appeal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formatGoal Context triple: [Twenty20 International cricket, formatGoal, increase spectator appeal]
-
A.
goalType
Indicates the specific category or nature of a goal associated with an entity or action.
-
B.
goalDescription
Indicates that an entity expresses, specifies, or provides a textual description of a goal or intended outcome associated with another entity or activity.
-
C.
statedAsGoalFor
chosen
Indicates that something has been explicitly declared or identified as a goal for a particular entity or context.
-
D.
narrativeGoal
Indicates that one entity has a desired outcome or objective within a story or narrative context that drives their actions or development.
-
E.
formerGoal
Indicates that an entity previously had a particular goal or objective, but no longer has it.
- 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_69d6aa864ed88190818280ab6791d065 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d77071492c8190bd6f8623a59464c9 |
completed | April 9, 2026, 9:25 a.m. |
| PD | Predicate disambiguation | batch_69d70d3f9dc88190a686a8b0dd6a3b21 |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:22 p.m.