Triple
T4761540
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indian Act |
E105707
|
entity |
| Predicate | currentDebate |
P57619
|
FINISHED |
| Object | repeal versus reform |
—
|
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: repeal versus reform | Statement: [Indian Act, currentDebate, repeal versus reform]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentDebate Context triple: [Indian Act, currentDebate, repeal versus reform]
-
A.
fieldOfDebate
Indicates that something is the subject or domain around which a debate or argumentative discussion is centered.
-
B.
debateTopic
Indicates that one entity serves as the subject or issue being discussed or argued about in a debate involving another entity.
-
C.
mainDebateTopic
chosen
Indicates that a specified subject or issue is the primary focus or central topic of a particular debate or discussion.
-
D.
inAcademicDebate
Indicates that one entity is engaged in a formal, scholarly argument or discussion with another entity, typically following academic norms and methods of reasoning.
-
E.
debatedWithin
Indicates that something is discussed or argued about within a particular group, context, or domain.
- 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_69bd43f14cac819081c7c69803648211 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd650eefe08190b99f9f01b121dbfd |
completed | March 20, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69bd6225c9488190afee5bb3619d0365 |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:20 p.m.