Triple
T13284926
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La montagne blanche |
E316417
|
entity |
| Predicate | authorNotableFact |
P8229
|
FINISHED |
| Object | Holocaust survivor |
—
|
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: Holocaust survivor | Statement: [La montagne blanche, authorNotableFact, Holocaust survivor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: authorNotableFact Context triple: [La montagne blanche, authorNotableFact, Holocaust survivor]
-
A.
notableFact
chosen
Indicates that there exists a particularly significant or noteworthy fact or piece of information associated with the subject.
-
B.
authorNotableWork
Indicates that a person is the creator or writer of a specific notable work, such as a book, article, or other significant publication.
-
C.
sonNotableFor
Indicates that a son is recognized or distinguished for a particular achievement, role, or characteristic.
-
D.
authorIsKnownFor
Indicates that a particular author is widely recognized or notable for a specific work, genre, contribution, or characteristic.
-
E.
notableFor
Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or role.
- 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_69d806b349908190a9a61dd9323bf153 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f6535688190a5a4549b7be2d611 |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:27 p.m.