Triple
T26310600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | French Algerian |
E661808
|
entity |
| Predicate | sharesCulturalElementsWith |
P22474
|
FINISHED |
| Object | Pied-Noir |
—
|
NE NERFINISHED |
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: Pied-Noir | Statement: [French Algerian, sharesCulturalElementsWith, Pied-Noir]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesCulturalElementsWith Context triple: [French Algerian, sharesCulturalElementsWith, Pied-Noir]
-
A.
culturalElements
Indicates a relationship where certain elements (such as practices, symbols, or artifacts) belong to, express, or characterize a particular culture or cultural context.
-
B.
culturallySimilarTo
chosen
Indicates that two entities share comparable cultural characteristics, practices, or values.
-
C.
sharesDesignTraditionWith
Indicates that two entities originate from or participate in the same design tradition, sharing common stylistic principles, methods, or heritage.
-
D.
sharesElementsWith
Indicates that two entities have one or more elements or components in common.
-
E.
sharesTraditionsWith
Indicates that two entities have customs, practices, or cultural traditions in common or mutually observe similar traditional activities.
- 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_69ee812dacfc81908484aade9120fba9 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f757898fe48190b124dc7301672623 |
completed | May 3, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69f754c484348190948d2a04ff228fb1 |
completed | May 3, 2026, 1:59 p.m. |
Created at: April 26, 2026, 10:22 p.m.