Triple
T38584614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Underbog |
E932317
|
entity |
| Predicate | entranceRequires |
P6140
|
FINISHED |
| Object | swimming through Coilfang Reservoir lake |
—
|
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: swimming through Coilfang Reservoir lake | Statement: [The Underbog, entranceRequires, swimming through Coilfang Reservoir lake]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: entranceRequires Context triple: [The Underbog, entranceRequires, swimming through Coilfang Reservoir lake]
-
A.
entranceTrait
Indicates a characteristic or feature associated with how an entity enters or is accessed (e.g., through a particular type or style of entrance).
-
B.
hasEntrance
chosen
Indicates that one entity possesses or provides an entry point or access way to another entity or space.
-
C.
guardedEntranceTo
Indicates that one entity serves as a protective or controlling barrier for access to another entity’s entrance.
-
D.
entranceVisibility
Indicates how easily or clearly an entrance can be seen or recognized from a given viewpoint or approach.
-
E.
hasEntranceRole
Indicates that an entity participates in an entrance or access point with a specific functional role or capacity.
- 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_69fce28d6c3081908bf76f5db63ecf68 |
completed | May 7, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69fce12d2f08819082134b5eb3db6a24 |
completed | May 7, 2026, 6:59 p.m. |
Created at: May 3, 2026, 4:32 p.m.