Triple
T37457887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Silence Priest |
E930843
|
entity |
| Predicate | tempoProfile |
P1368
|
FINISHED |
| Object | strong early to mid game |
—
|
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: strong early to mid game | Statement: [Silence Priest, tempoProfile, strong early to mid game]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tempoProfile Context triple: [Silence Priest, tempoProfile, strong early to mid game]
-
A.
timeProfile
Indicates the temporal pattern or schedule according to which an action, process, or relationship occurs or is distributed over time.
-
B.
tempo
chosen
Indicates the speed or pace at which an action, process, or sequence unfolds over time.
-
C.
tempoTool
Indicates a tool or method used to control, measure, or modify the tempo of an action, process, or performance.
-
D.
tempoConcept
Indicates a relationship where something embodies, defines, or is characterized by a particular concept of tempo or speed.
-
E.
tempoFeature
Indicates a relationship where a musical or rhythmic element is characterized by, or associated with, a specific tempo-related property or feature.
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbacaf54648190811ea33b34907e8e |
completed | May 6, 2026, 9:03 p.m. |
| PD | Predicate disambiguation | batch_69fba883f770819091059c6f6c6af9f7 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:17 p.m.