Triple
T6573656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Île d’Orléans |
E155503
|
entity |
| Predicate | belongsToCulturalIdentity |
P1439
|
FINISHED |
| Object | Québécois heritage |
—
|
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: Québécois heritage | Statement: [Île d’Orléans, belongsToCulturalIdentity, Québécois heritage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToCulturalIdentity Context triple: [Île d’Orléans, belongsToCulturalIdentity, Québécois heritage]
-
A.
hasStrongCulturalIdentity
Indicates that an entity possesses a well-defined, deeply rooted, and strongly maintained sense of belonging to a particular culture or cultural tradition.
-
B.
hasAssociatedCulture
chosen
Indicates that an entity is related to, influenced by, or characterized by a particular culture.
-
C.
hasCulturalRelation
Indicates a relationship in which entities are connected through shared, influencing, or interacting cultural practices, values, traditions, or expressions.
-
D.
cultureOfOrigin
Indicates the cultural background or tradition from which an entity originates or is derived.
-
E.
hasDistinctCultureFrom
Indicates that the culture of one entity is different and distinguishable from the culture of another 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_69c688151254819080387f87deab8fa7 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6cc9c6cb0819084fec8e0beb430de |
completed | March 27, 2026, 6:29 p.m. |
| PD | Predicate disambiguation | batch_69c6acf93cb48190b54f5dd6febd34dc |
completed | March 27, 2026, 4:14 p.m. |
Created at: March 27, 2026, 1:53 p.m.