Triple
T36340765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | French World War memorials |
E894914
|
entity |
| Predicate | commonSymbol |
P18980
|
FINISHED |
| Object | poilu (French infantryman) |
—
|
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: poilu (French infantryman) | Statement: [French World War memorials, commonSymbol, poilu (French infantryman)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonSymbol Context triple: [French World War memorials, commonSymbol, poilu (French infantryman)]
-
A.
typicalSymbol
chosen
Indicates that something serves as a characteristic or commonly recognized symbol representing something else.
-
B.
exampleSymbol
Indicates that there is a generic or placeholder relationship between entities, used as an example rather than a specific, defined interaction.
-
C.
commonSign
Indicates that multiple entities share the same sign, symbol, or indicator in common.
-
D.
commonIn
Indicates that something frequently occurs, appears, or is found within a specified context, group, or environment.
-
E.
symbolizes
Indicates that one entity stands for, represents, or is used as a sign for another entity, concept, or idea.
- 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_69ff0214d7348190904688376df99bce |
completed | May 9, 2026, 9:44 a.m. |
| PD | Predicate disambiguation | batch_69feffd62fec8190a855922c8b3c57cf |
completed | May 9, 2026, 9:35 a.m. |
Created at: May 3, 2026, 4:09 p.m.