Triple
T34275835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | d’Étanges |
E879451
|
entity |
| Predicate | hasCountryOfLiteraryOrigin |
P36448
|
FINISHED |
| Object | Germany |
E1728
|
NE 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: Germany | Statement: [d’Étanges, hasCountryOfLiteraryOrigin, Germany]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCountryOfLiteraryOrigin Context triple: [d’Étanges, hasCountryOfLiteraryOrigin, Germany]
-
A.
literaryOriginCountry
chosen
Indicates the country from which a literary work or literary tradition originally comes.
-
B.
hasLiteraryOriginAuthorNationality
Indicates that the nationality of the author from whom a work or concept originates is being specified.
-
C.
countryOfNotableWork
Indicates the country with which a notable work is primarily associated, such as where it was created, set, or gained its significance.
-
D.
writtenInCountry
Indicates that a written work was created, authored, or composed within the geographical boundaries of a specific country.
-
E.
workOfFictionDebutCountry
Indicates the country where a work of fiction was first released, published, or debuted.
- F. None of above.
Provenance (4 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_69f349b5f6648190b9420d94a4cd16e0 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a37181498a08190acc9a260feb3dba7 |
completed | June 20, 2026, 10:45 p.m. |
| PD | Predicate disambiguation | batch_6a0379fbe4a08190bfe65ebd141164e9 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:56 a.m.