Triple
T7821608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red Faber |
E181141
|
entity |
| Predicate | allowedToContinueSpitballAfterBan |
P79190
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Red Faber, allowedToContinueSpitballAfterBan, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowedToContinueSpitballAfterBan Context triple: [Red Faber, allowedToContinueSpitballAfterBan, true]
-
A.
tieAllowedAfterRegulation
Indicates that a tie outcome is permitted to occur after the application or completion of a specified regulation or regulatory process.
-
B.
bannedAfter
Indicates that one entity becomes prohibited or forbidden only after the occurrence or establishment of another specified entity or event.
-
C.
ballOutOfPlayCondition
Indicates that the conditions under which the ball is considered out of play are satisfied.
-
D.
kickingAllowed
Indicates that performing or engaging in kicking is permitted within the specified context or under the given conditions.
-
E.
ballMustExit
Indicates that the ball is required to leave or move out of a specified area, state, or context.
- F. None of above. chosen
Provenance (4 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_69ca828153f48190bdb27ac46f8e0745 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cafa083fe88190a77efb7cfee4bd6f |
completed | March 30, 2026, 10:32 p.m. |
| PD | Predicate disambiguation | batch_69cae91ae008819098e56bbe51143b31 |
completed | March 30, 2026, 9:20 p.m. |
| PDg | Predicate description generation | batch_69caf7855a3c81908b9318f7186fc0c0 |
completed | March 30, 2026, 10:21 p.m. |
Created at: March 30, 2026, 4:41 p.m.