Triple
T36340764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | French World War memorials |
E894914
|
entity |
| Predicate | typicalLanguageOfInscriptions |
P15804
|
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: [French World War memorials, typicalLanguageOfInscriptions, French]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalLanguageOfInscriptions Context triple: [French World War memorials, typicalLanguageOfInscriptions, French]
-
A.
officialLanguageOfInscriptions
Indicates the language officially used in the inscriptions associated with a particular entity.
-
B.
secondaryLanguageOfInscriptions
Indicates that a specified language serves as the secondary language used in the inscriptions associated with a given entity.
-
C.
inscriptionsLanguage
chosen
Indicates that the language used in the inscriptions on an object or surface is the specified language.
-
D.
typicalLanguageOfReadings
Indicates the language that is most commonly used for readings or interpretations associated with a given entity.
-
E.
languageAttestedIn
Indicates that evidence exists showing the use or presence of a particular language in a specified place, time, or context.
- 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_69f76e4e90148190b02fe52593c70b5b |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0a54cc8190868c1bfa1590d1a6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:09 p.m.