Triple
T14027710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Val-d’Or Foreurs |
E337503
|
entity |
| Predicate | primaryFanBaseLanguage |
P3778
|
FINISHED |
| Object | French |
—
|
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: French | Statement: [Val-d’Or Foreurs, primaryFanBaseLanguage, French]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryFanBaseLanguage Context triple: [Val-d’Or Foreurs, primaryFanBaseLanguage, French]
-
A.
languageOfFanbase
chosen
Indicates the primary language or languages commonly used by a fanbase in its communication and expression.
-
B.
hasFanBasePrimarilyIn
Indicates that an entity’s main or largest group of supporters, followers, or fans is located in a specified place or region.
-
C.
primaryLanguageOf
Indicates that a specified language is the main or official language used by a particular entity (such as a person, organization, or region).
-
D.
hasFanBaseFrom
Indicates that an entity has a significant group of supporters or followers originating from a specified place, group, or source.
-
E.
majorityLanguageOf
Indicates that a given language is the primary or most widely spoken language within a specified group, region, or entity.
- 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_69d81c6543a48190bd5ba93d7419e797 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2fa830ac81908cb7df7c9e81e42a |
completed | April 14, 2026, 12:14 p.m. |
| PD | Predicate disambiguation | batch_69de05ab36b48190920efb1869bdb1fe |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:20 p.m.