Triple
T36479557
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Detroit City FC |
E898770
|
entity |
| Predicate | matchdayFeatures |
P44508
|
FINISHED |
| Object | chants |
—
|
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: chants | Statement: [Detroit City FC, matchdayFeatures, chants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: matchdayFeatures Context triple: [Detroit City FC, matchdayFeatures, chants]
-
A.
matchdayElement
Indicates a relationship where an element (such as a game, event, or component) is part of or associated with a specific matchday.
-
B.
typicalMatchDay
Indicates that the relationship or conditions described correspond to what normally happens on a standard or usual match day.
-
C.
matchdayActivity
chosen
Indicates the specific activity, event, or engagement that takes place in connection with a particular match day.
-
D.
matchdayLocation
Indicates the venue or place where a particular matchday or game is held.
-
E.
featuresCompetitionIn
Indicates that something includes or presents a particular competition as part of its content or structure.
- 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_69f76e5a0e088190a2b6706aeb41723c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fb3425666081908916fcbf3b5dd907 |
completed | May 6, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69fb2f5f3164819099429c2cc3d24e01 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:10 p.m.