Triple
T5637818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Voice of Fire |
E124190
|
entity |
| Predicate | associatedWithDebateOn |
P50993
|
FINISHED |
| Object | public arts funding in Canada |
—
|
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: public arts funding in Canada | Statement: [Voice of Fire, associatedWithDebateOn, public arts funding in Canada]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithDebateOn Context triple: [Voice of Fire, associatedWithDebateOn, public arts funding in Canada]
-
A.
relatedToDebate
chosen
Indicates a relationship in which something is connected or relevant to a debate, discussion, or argumentative exchange.
-
B.
debatedWithin
Indicates that something is discussed or argued about within a particular group, context, or domain.
-
C.
hasDebatedPerson
Indicates that one person has engaged in a debate or formal argumentative discussion with another person.
-
D.
hasDebate
Indicates that there is a formal discussion or argument between entities, typically presenting opposing viewpoints on a topic.
-
E.
partOfDebate
Indicates that one entity is a component, segment, or participant within a larger debate or argumentative exchange.
- 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_69c00824643c81909ffdb888a2d35189 |
completed | March 22, 2026, 3:17 p.m. |
| NER | Named-entity recognition | batch_69c022820b7c81908f79c0a124d6b940 |
completed | March 22, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69c01b1f12ec8190b4b9d9ee31cabe19 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:41 p.m.