Triple
T36340771
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | French World War memorials |
E894914
|
entity |
| Predicate | commonInscription |
P105548
|
FINISHED |
| Object | "À nos morts" |
—
|
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: "À nos morts" | Statement: [French World War memorials, commonInscription, "À nos morts"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonInscription Context triple: [French World War memorials, commonInscription, "À nos morts"]
-
A.
commonlyInscribedIn
chosen
Indicates that something is typically written, carved, or engraved onto a particular surface, object, or medium.
-
B.
inscriptionsCelebrate
Indicates that the content of inscriptions expresses praise, commemoration, or honor toward a person, event, or entity.
-
C.
materialTypicallyInscribedOn
Indicates the material that is most commonly used as the surface or medium on which something is inscribed.
-
D.
issuedInscriptionsIn
Indicates that an entity (such as an authority or issuer) produced or authorized inscriptions within a specified place or context.
-
E.
issuedInscription
Indicates that an authority or source formally created and released a specific inscription or written record.
- 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_69ff0491409c8190be40f633a58da0b1 |
completed | May 9, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_69ff040bb5cc81909534c7eee85d5e90 |
completed | May 9, 2026, 9:53 a.m. |
Created at: May 3, 2026, 4:09 p.m.