Triple
T37472437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sanguine Depths |
E931186
|
entity |
| Predicate | zoneEnvironment |
P134479
|
FINISHED |
| Object | Revendreth |
—
|
NE NERFINISHED |
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: Revendreth | Statement: [Sanguine Depths, zoneEnvironment, Revendreth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: zoneEnvironment Context triple: [Sanguine Depths, zoneEnvironment, Revendreth]
-
A.
zone
Indicates that an entity is located within, associated with, or assigned to a particular geographic or conceptual area or zone.
-
B.
rangeEnvironment
chosen
Indicates that an entity operates or exists within a specified environmental range or conditions.
-
C.
zoneType
Indicates the classification or category of a zone that specifies its type or functional designation.
-
D.
zoneBased
Indicates that the relationship or action is determined or constrained by specific geographic or logical zones.
-
E.
zoneBehavior
Indicates how an entity is expected to act or be treated within a specific zone or area.
- 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_69f76ec2af148190897d101070d7f415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba68077788190b311e027435fcf87 |
completed | May 6, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fba34c65ac8190b298f0f00d1dcc0e |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.