Triple
T37539077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Azuremyst Isle |
E933279
|
entity |
| Predicate | secondaryInhabitants |
P172822
|
FINISHED |
| Object | Stillpine furbolgs |
—
|
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: Stillpine furbolgs | Statement: [Azuremyst Isle, secondaryInhabitants, Stillpine furbolgs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondaryInhabitants Context triple: [Azuremyst Isle, secondaryInhabitants, Stillpine furbolgs]
-
A.
otherInhabitants
chosen
Indicates that there exist additional beings or residents associated with or present in the same place, group, or context as a referenced entity.
-
B.
secondaryLivestock
Indicates that the referenced livestock are of secondary or lesser importance in relation to a primary group of livestock.
-
C.
rearsSpecies
Indicates that one entity raises, breeds, or cultivates individuals belonging to a particular species.
-
D.
inhabitedBy
Indicates that a place or location is lived in or occupied by a particular individual, group, or species.
-
E.
subordinateSpecies
Indicates that one species is hierarchically or functionally subordinate to another species within a defined biological or ecological context.
- 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_69f76ec999288190ae26ec7b6aea7046 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff90b673248190b4dda9e005642d17 |
completed | May 9, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69ff8d5bee1081909274052945e98a6f |
completed | May 9, 2026, 7:39 p.m. |
Created at: May 3, 2026, 4:17 p.m.