Triple
T17052460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maple Leaf |
E413732
|
entity |
| Predicate | prominentlyAdoptedOnFlagYear |
P3297
|
FINISHED |
| Object | 1965 |
—
|
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: 1965 | Statement: [Maple Leaf, prominentlyAdoptedOnFlagYear, 1965]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: prominentlyAdoptedOnFlagYear Context triple: [Maple Leaf, prominentlyAdoptedOnFlagYear, 1965]
-
A.
adoptedProminentlyBy
Indicates that something (such as an idea, practice, or technology) has been widely and visibly taken up or embraced by a particular group or entity.
-
B.
introducedInYear
chosen
Indicates the year in which something was first introduced, launched, or made available.
-
C.
conventionAdoptedAt
Indicates that a convention was formally adopted or agreed upon at a specific event, meeting, or location.
-
D.
proposedInYear
Indicates that something, such as a plan, idea, or piece of legislation, was formally put forward or suggested in a specific calendar year.
-
E.
resolutionAdoptionYear
Indicates the year in which a resolution was formally adopted.
- 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_69d886cde3d481908d4d01ba88ba7eb7 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3daa3324881908d9e445ba1cfe109 |
completed | April 18, 2026, 7:25 p.m. |
| PD | Predicate disambiguation | batch_69e35d60a588819084f53ef9f8b2e7c0 |
completed | April 18, 2026, 10:30 a.m. |
Created at: April 10, 2026, 5:34 a.m.