Triple
T13812109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Place Blanche |
E331917
|
entity |
| Predicate | streetAddressLanguage |
P24399
|
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: [Place Blanche, streetAddressLanguage, French]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: streetAddressLanguage Context triple: [Place Blanche, streetAddressLanguage, French]
-
A.
officialLanguageOfListing
Indicates that a specified language is the official language used in a particular listing.
-
B.
standardLanguageOf
Indicates that one entity serves as the officially recognized or commonly used standard language for another entity (such as a country, region, or organization).
-
C.
primaryLanguageSide1
Indicates that the specified language is the main or dominant language associated with the first participant or side in a relationship.
-
D.
regionLanguage
Indicates that a particular language is used or officially recognized within a specific geographic region.
-
E.
hasLanguageOfToponym
chosen
Indicates that a place name (toponym) is expressed in or associated with a particular language.
- 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_69d81c59f8808190a851bc56afdc55e9 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de027198f8819095da3e714ac241f5 |
completed | April 14, 2026, 9:01 a.m. |
| PD | Predicate disambiguation | batch_69dbc862e9608190bd8a3d883959b7e4 |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:12 p.m.