Triple
T35051157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blades |
E1011331
|
entity |
| Predicate | operationalStatusInSkyrim |
P5870
|
FINISHED |
| Object | nearly destroyed |
—
|
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: nearly destroyed | Statement: [Blades, operationalStatusInSkyrim, nearly destroyed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operationalStatusInSkyrim Context triple: [Blades, operationalStatusInSkyrim, nearly destroyed]
-
A.
operatingStatus
chosen
Indicates whether an entity is currently functioning, active, or in service versus inactive, closed, or out of service.
-
B.
legalStatusAmongBosmer
Indicates the legal standing or classification of an entity within Bosmer (Wood Elf) society or law.
-
C.
FrontierStatus
Indicates the status or condition of something in relation to a boundary, edge, or frontier context (such as being at, beyond, or within that frontier).
-
D.
operatorStatus
Indicates the current operational state or condition of an operator (e.g., active, inactive, or in error).
-
E.
runtimeStatus
Indicates the current operational state or condition of an entity while it is running or executing.
- 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_69f76dcfdda48190b1ebae5da8b54f12 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a0120f070b081909b6d1a3d8ee6b80e |
completed | May 11, 2026, 12:21 a.m. |
| PD | Predicate disambiguation | batch_6a01209da37481909683e38f264b15ef |
completed | May 11, 2026, 12:19 a.m. |
Created at: May 3, 2026, 4:01 p.m.