Triple
T35928259
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spartani |
E1039082
|
entity |
| Predicate | chantUsage |
P175621
|
FINISHED |
| Object | used in arena 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: used in arena chants | Statement: [Spartani, chantUsage, used in arena chants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chantUsage Context triple: [Spartani, chantUsage, used in arena chants]
-
A.
usedAsChant
chosen
Indicates that something (typically a phrase, text, or sound) is employed as a chant in a ritual, performance, or repetitive vocal practice.
-
B.
usagePattern
Indicates how something is typically used or the recurring manner in which it is employed or consumed.
-
C.
promotionUsage
Indicates that a promotion is being applied or used in relation to a particular transaction, context, or entity.
-
D.
beatUsedIn
Indicates that a particular beat or rhythmic pattern is employed within a specific musical piece, section, or context.
-
E.
usageType
Indicates the specific manner, purpose, or context in which something is used or intended to be used.
- 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_69f76e23e4688190a5369138755138bf |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7ac23d1388190bdf9628b294943bd |
completed | May 3, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f7ab734d848190a84f9b8c3a952b75 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 3, 2026, 4:07 p.m.