Triple
T11542326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blackwing Lair |
E273701
|
entity |
| Predicate | recommendedLevelOriginal |
P65817
|
FINISHED |
| Object | 60 |
—
|
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: 60 | Statement: [Blackwing Lair, recommendedLevelOriginal, 60]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recommendedLevelOriginal Context triple: [Blackwing Lair, recommendedLevelOriginal, 60]
-
A.
traditionalLevel
Indicates the degree to which something adheres to established customs, practices, or traditions.
-
B.
minimumLevel
chosen
Indicates that one entity specifies the lowest allowable or required level, degree, or threshold at which another entity, condition, or action becomes valid or applicable.
-
C.
intendedReadingLevel
Indicates the reading proficiency or audience level that a text or resource is designed or meant to be understood by.
-
D.
exportLevel
Indicates the degree or extent to which something is produced in one place and sent out or made available to other places or markets.
-
E.
representedLevel
Indicates that one entity denotes or encodes the degree, intensity, or value (i.e., the level) of another entity or property.
- 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_69d6aae4dfa48190a3ab0b19a159a3c5 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d886e09eec8190894069d86b79183d |
completed | April 10, 2026, 5:13 a.m. |
| PD | Predicate disambiguation | batch_69d80879fdb48190be6dacc8aa63c809 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:37 p.m.