Triple
T38582827
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Forbidding Sea |
E932282
|
entity |
| Predicate | dangerLevelInLore |
P173423
|
FINISHED |
| Object | high |
—
|
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: high | Statement: [Forbidding Sea, dangerLevelInLore, high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dangerLevelInLore Context triple: [Forbidding Sea, dangerLevelInLore, high]
-
A.
dangerToWorld
Indicates a relationship where something poses a threat or potential harm to the world as a whole.
-
B.
threatLevelInNarrative
chosen
Indicates the degree of danger or risk that a subject poses or experiences within the context of a narrative or storyline.
-
C.
dangerWarning
Indicates that one entity issues or represents a warning about potential danger associated with another entity or situation.
-
D.
threatLevelEarlyGame
Indicates the degree of danger or pressure an entity poses to others during the early phase of a game or scenario.
-
E.
thrillLevel
Indicates the degree of excitement or intensity of exhilaration associated with an experience, action, or situation.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdaa36f90819093f8661969990c7d |
completed | May 7, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fefc588190b063d7ea1ec87b07 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:32 p.m.