Triple
T458283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toronto Argonauts |
E7278
|
entity |
| Predicate | fandomDemonym |
P191
|
FINISHED |
| Object | Argos fans |
—
|
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: Argos fans | Statement: [Toronto Argonauts, fandomDemonym, Argos fans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fandomDemonym Context triple: [Toronto Argonauts, fandomDemonym, Argos fans]
-
A.
hasDemonym
chosen
Indicates that one entity is the term (demonym) used to refer to the inhabitants or natives of another entity (typically a place).
-
B.
ethnonym
Indicates that one entity is the name of an ethnic group used to refer to the people associated with another entity.
-
C.
eraName
Indicates the named historical or chronological era associated with an entity or time period.
-
D.
demographicScope
Indicates the specific population group or demographic segment to which something (e.g., a policy, study, product, or service) is targeted or applicable.
-
E.
nameDayRegion
Indicates the region or geographic area in which a particular name day is observed or recognized.
- 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_69a2efa3163081909acff040a22bd559 |
completed | Feb. 28, 2026, 1:37 p.m. |
| PD | Predicate disambiguation | batch_69a2ede75b6c81908350103d21f22a03 |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.