Triple
T7117889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tiges |
E165864
|
entity |
| Predicate | associatedWithChant |
P15355
|
FINISHED |
| Object | Yellow and Black |
—
|
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: Yellow and Black | Statement: [Tiges, associatedWithChant, Yellow and Black]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithChant Context triple: [Tiges, associatedWithChant, Yellow and Black]
-
A.
hasChant
chosen
Indicates that an entity is associated with or characterized by a particular chant.
-
B.
alsoChantedIn
Indicates that a chant, hymn, or recitation is performed or used in an additional context, location, or tradition beyond its primary one.
-
C.
associatedWithHymns
Indicates that something has a connection or relationship to hymns, such as being used in, derived from, or thematically linked to them.
-
D.
chantingIs24x7
Indicates that the chanting activity occurs continuously, 24 hours a day, 7 days a week.
-
E.
associatedWithSupportersSong
Indicates that there is a relationship between an entity and a supporters’ song, such as being linked to, represented by, or commonly accompanied by that song.
- 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_69c6888227bc8190a1394679e3116f90 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e618bdac8190be291468b7d977bb |
completed | March 27, 2026, 8:18 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c4f9788190830288d00cc37026 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:43 p.m.