Triple
T38387237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mélisande |
E899609
|
entity |
| Predicate | nationalityOfOriginContext |
P56388
|
FINISHED |
| Object | Belgian literary tradition |
—
|
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: Belgian literary tradition | Statement: [Mélisande, nationalityOfOriginContext, Belgian literary tradition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nationalityOfOriginContext Context triple: [Mélisande, nationalityOfOriginContext, Belgian literary tradition]
-
A.
nationalityOfPersonReferredTo
Indicates that one entity is the country or nationality associated with the person referenced by the other entity.
-
B.
cultureOfOrigin
chosen
Indicates the cultural background or tradition from which an entity originates or is derived.
-
C.
originalNationality
Indicates the country or nationality an entity initially belonged to or originated from, before any later changes in citizenship or affiliation.
-
D.
nationalityInText
Indicates that a person's nationality is mentioned or specified within a given text.
-
E.
countryOfHeritage
Indicates the country from which an entity’s cultural, ancestral, or familial heritage originates.
- 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_69f76e5c9b808190b486523f5c2f817d |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fe72dca2f08190beff17de3d2aada6 |
completed | May 8, 2026, 11:33 p.m. |
| PD | Predicate disambiguation | batch_69fe70bca8d08190b810e1e616ceac44 |
completed | May 8, 2026, 11:24 p.m. |
Created at: May 3, 2026, 4:31 p.m.