Triple
T15912558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saga of Sigurd the Crusader |
E385883
|
entity |
| Predicate | literaryLanguageFamily |
P57275
|
FINISHED |
| Object | North Germanic languages |
—
|
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: North Germanic languages | Statement: [Saga of Sigurd the Crusader, literaryLanguageFamily, North Germanic languages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: literaryLanguageFamily Context triple: [Saga of Sigurd the Crusader, literaryLanguageFamily, North Germanic languages]
-
A.
languageFamily
Indicates that two or more languages belong to the same genealogical language family or linguistic lineage.
-
B.
languageFamilyOfWork
chosen
Indicates that a work belongs to or is classified under a particular language family.
-
C.
languageFamilyWritten
Indicates that one language family is represented or recorded in a particular written form or script.
-
D.
inLanguageFamily
Indicates that two languages belong to the same linguistic family or classification.
-
E.
literaryLanguage
Indicates that an entity is expressed, written, or communicated using a particular literary or standardized written language.
- 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_69d86da686e4819097cbf3b1fc2d881d |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e172b48b308190bc430b2308cbc75b |
completed | April 16, 2026, 11:37 p.m. |
| PD | Predicate disambiguation | batch_69e142cf5c548190a931f7b58144cd31 |
completed | April 16, 2026, 8:13 p.m. |
Created at: April 10, 2026, 4:52 a.m.