Triple
T462779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canadian English |
E7376
|
entity |
| Predicate | typicalVocabularyItem |
P5695
|
FINISHED |
| Object | loonie |
—
|
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: loonie | Statement: [Canadian English, typicalVocabularyItem, loonie]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalVocabularyItem Context triple: [Canadian English, typicalVocabularyItem, loonie]
-
A.
lexicalItem
chosen
Indicates that one entity is a word or vocabulary unit associated with, or used to express, another entity (such as a concept, meaning, or linguistic entry).
-
B.
typicalIn
Indicates that something commonly occurs, appears, or is found within a given context, category, or environment.
-
C.
keyTerm
Indicates that a term functions as a primary or central concept within a given context or information structure.
-
D.
movementVocabulary
Indicates a relationship where an entity possesses or uses a characteristic set of movement patterns, gestures, or motion styles as its expressive or functional "vocabulary."
-
E.
lexicalChange
Indicates a relationship where one linguistic form is replaced, modified, or evolves into another form over time or across language varieties.
- 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_69a2e7e5c5bc8190a1dc8178218fba40 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2efc09eac8190add4bb5823b53ba7 |
completed | Feb. 28, 2026, 1:38 p.m. |
| PD | Predicate disambiguation | batch_69a2ede8eac081908dffade6a5e7950b |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.