Triple
T14661261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nilsu |
E344244
|
entity |
| Predicate | hasVariantOrigin |
P3654
|
FINISHED |
| Object | Scandinavian |
—
|
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: Scandinavian | Statement: [Nilsu, hasVariantOrigin, Scandinavian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVariantOrigin Context triple: [Nilsu, hasVariantOrigin, Scandinavian]
-
A.
hasVariant
Indicates that one entity exists as an alternative form, version, or variation of another entity.
-
B.
hasOriginIn
chosen
Indicates that something begins, arises, or is derived from a specified source, place, or cause.
-
C.
hasOriginFeature
Indicates that an entity possesses a specific characteristic, attribute, or feature related to its origin or source.
-
D.
hasVariantSystem
Indicates that one system is an alternative or variant form of another system within the same general framework or category.
-
E.
hasVariantsIn
Indicates that an entity exists in multiple alternative forms or versions within a specified context or set.
- 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_69d822e283fc8190a0e4c235cf880052 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb51c84448190a1f5fa9ab8a1e2c4 |
completed | April 14, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69de6576f0208190aa94d995e797ac38 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:27 a.m.