Triple
T37750458
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Girdle of Melian |
E940966
|
entity |
| Predicate | realmTypeProtected |
P15837
|
FINISHED |
| Object | hidden Elven realm |
—
|
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: hidden Elven realm | Statement: [Girdle of Melian, realmTypeProtected, hidden Elven realm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: realmTypeProtected Context triple: [Girdle of Melian, realmTypeProtected, hidden Elven realm]
-
A.
realmType
chosen
Indicates the classification or category of a realm, specifying what kind or type of realm it is.
-
B.
protectedRealmWith
Indicates that one entity is a realm or domain that is safeguarded or secured in conjunction with, or by means of, another entity.
-
C.
realmRole
Indicates that an entity holds or is associated with a specific role or set of permissions within a defined realm or security domain.
-
D.
realmTypeConnected
Indicates that two realm types are linked or associated in a way that allows interaction, transition, or shared properties between them.
-
E.
realmTypeObservedFrom
Indicates that the type or category of a realm is determined or identified based on observations made from a particular source or viewpoint.
- 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_69f76ee1f3a88190834e6c8af99bccc9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbaef0cec881908c2742d77d145901 |
completed | May 6, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69fbadf632ec8190b14991c971258307 |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:19 p.m.