Triple
T8275259
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The 12s |
E193529
|
entity |
| Predicate | supportsDuring |
P1853
|
FINISHED |
| Object | regular season games |
—
|
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: regular season games | Statement: [The 12s, supportsDuring, regular season games]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsDuring Context triple: [The 12s, supportsDuring, regular season games]
-
A.
supportedAfter
Indicates that one entity provided support to another only after a specified event, time, or condition had occurred.
-
B.
supportAgainst
Indicates providing help, resources, or advocacy to oppose or resist a particular target, threat, or adversary.
-
C.
supportedDuringWar
Indicates that one entity provided assistance, resources, or backing to another entity specifically during a time of war.
-
D.
supportsReach
Indicates that one entity enables, facilitates, or maintains the ability of another entity to extend its influence, access, or coverage to additional targets or areas.
-
E.
support
chosen
Indicates that one entity provides assistance, endorsement, or backing to another entity or its actions.
- 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_69ca82e14ae481908ffdb822cd2192bc |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb798bc29c8190927ef4b0662d6b98 |
completed | March 31, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69cb70a4525481909399d313a6247ace |
completed | March 31, 2026, 6:58 a.m. |
Created at: March 30, 2026, 5:51 p.m.