Triple
T38582816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Forbidding Sea |
E932282
|
entity |
| Predicate | surroundsPartOf |
P7850
|
FINISHED |
| Object | Azeroth |
—
|
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: Azeroth | Statement: [Forbidding Sea, surroundsPartOf, Azeroth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: surroundsPartOf Context triple: [Forbidding Sea, surroundsPartOf, Azeroth]
-
A.
surrounds
chosen
Indicates that one entity is located all around another entity, enclosing or encircling it on multiple sides or completely.
-
B.
partlyEncircles
Indicates that one entity surrounds another along a substantial but incomplete portion of its boundary or perimeter.
-
C.
containedPartOf
Indicates that one entity is physically or logically included within and forms a part of another entity.
-
D.
surroundedOnThreeSidesBy
Indicates that one entity is positioned so that three of its sides are directly bordered or enclosed by another entity.
-
E.
surroundedButDidNotInclude
Indicates that one entity completely encircled another in space or extent, while explicitly excluding that inner entity from its own area or membership.
- 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_69fcdaa36f90819093f8661969990c7d |
completed | May 7, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fefc588190b063d7ea1ec87b07 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:32 p.m.