Triple
T29538164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frostborn |
E749407
|
entity |
| Predicate | settingInfluence |
P152787
|
FINISHED |
| Object | Viking culture |
—
|
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: Viking culture | Statement: [Frostborn, settingInfluence, Viking culture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: settingInfluence Context triple: [Frostborn, settingInfluence, Viking culture]
-
A.
influenceOf
Indicates that one entity affects, shapes, or alters the state, behavior, or properties of another entity.
-
B.
incorporatesInfluence
chosen
Indicates that one entity integrates or absorbs the influence, ideas, or characteristics of another into itself.
-
C.
ruleInfluence
Indicates that one rule affects, constrains, or modifies the behavior, outcome, or applicability of another rule.
-
D.
designInfluenceOn
Indicates that one design, designer, or design-related factor has an effect on shaping, guiding, or altering another design or design outcome.
-
E.
featuresInfluence
Indicates that certain features or characteristics have an effect on or contribute to changes in other features, outcomes, or behaviors.
- 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_69f0bd47abb081909bd6e6a33d770fd8 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f7117e55908190a67105e92bc4830f |
completed | May 3, 2026, 9:12 a.m. |
| PD | Predicate disambiguation | batch_69f70f380690819090cc34763ba460ed |
completed | May 3, 2026, 9:02 a.m. |
Created at: April 28, 2026, 5 p.m.