Triple
T38643703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Warfronts |
E938664
|
entity |
| Predicate | hasDifficultySetting |
P201164
|
FINISHED |
| Object | single baseline difficulty |
—
|
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: single baseline difficulty | Statement: [Warfronts, hasDifficultySetting, single baseline difficulty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDifficultySetting Context triple: [Warfronts, hasDifficultySetting, single baseline difficulty]
-
A.
hasDifficultyClass
Indicates that something (such as a task, challenge, or problem) is associated with a specific level of difficulty or complexity.
-
B.
hasDifficultyContext
Indicates that something’s difficulty is defined, interpreted, or constrained within a particular situational or contextual framework.
-
C.
hasDifficultyDescription
Indicates that an entity is associated with a textual description explaining its level or nature of difficulty.
-
D.
hasDifficultyEffect
Indicates that one entity causes a change in the difficulty level or challenge associated with another entity or activity.
-
E.
hasMeasurementDifficulty
Indicates that performing a measurement on something is challenging or problematic in some way.
- F. None of above. chosen
Provenance (4 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_69f76ed948ec81908ce7811608a8f359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ffcc6182b48190afb598ced6500e66 |
completed | May 10, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69ffcbb363748190bc6f8d038fba44ff |
completed | May 10, 2026, 12:05 a.m. |
| PDg | Predicate description generation | batch_69ffcc60dae48190b76b3eb7e2ce5103 |
completed | May 10, 2026, 12:08 a.m. |
Created at: May 3, 2026, 4:32 p.m.