Triple
T24469857
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Crimson Crew |
E617068
|
entity |
| Predicate | primaryEventType |
P156223
|
FINISHED |
| Object | home 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: home games | Statement: [The Crimson Crew, primaryEventType, home games]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryEventType Context triple: [The Crimson Crew, primaryEventType, home games]
-
A.
primaryType
Indicates the main or most fundamental category or classification assigned to an entity, distinguishing it from any secondary or auxiliary types.
-
B.
primaryCauseCategory
Indicates the main type or classification of cause responsible for an outcome or event.
-
C.
primaryContainmentType
Indicates the main method or structure used to hold, enclose, or confine one entity within another.
-
D.
primaryCatch
Indicates that an entity is the main or most significant target, recipient, or object captured or obtained in a given context.
-
E.
primaryIntent
Indicates the main purpose, goal, or motivation underlying an action, event, or relationship among entities.
- 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_69e2d7f197588190889a03e620558059 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f299422cdc8190bc8d56243b7bc313 |
completed | April 29, 2026, 11:50 p.m. |
| PD | Predicate disambiguation | batch_69f287d76c7c81909494f12e606a9149 |
completed | April 29, 2026, 10:36 p.m. |
| PDg | Predicate description generation | batch_69f28f4d978c81908310c01def2514cc |
completed | April 29, 2026, 11:07 p.m. |
Created at: April 18, 2026, 2:20 a.m.