Triple
T17979183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nahusha |
E449554
|
entity |
| Predicate | realmFallenTo |
P129981
|
FINISHED |
| Object | forest |
—
|
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: forest | Statement: [Nahusha, realmFallenTo, forest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: realmFallenTo Context triple: [Nahusha, realmFallenTo, forest]
-
A.
realm
Indicates that one entity is a domain, sphere of influence, or area of control associated with another entity.
-
B.
fellOn
Indicates that one entity moved downward, typically due to gravity, and came to rest on the surface of another entity.
-
C.
realmRuled
Indicates that one entity serves as the sovereign or governing ruler over a particular realm, territory, or domain.
-
D.
deathRealm
Indicates a realm, domain, or state specifically associated with death or the dead.
-
E.
underTheReignOf
Indicates that one entity existed or operated during the period when another entity (typically a ruler or authority) held power or governance.
- F. None of above. chosen
Provenance (4 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_69d8b9f9927c8190a006110c8b996e61 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4b201d1508190a9d6abbfd04bdcae |
completed | April 19, 2026, 10:44 a.m. |
| PD | Predicate disambiguation | batch_69e3f8fa62688190a5d5c361ab896256 |
completed | April 18, 2026, 9:34 p.m. |
| PDg | Predicate description generation | batch_69e42d8d68288190a05dc5d7803cf823 |
completed | April 19, 2026, 1:19 a.m. |
Created at: April 10, 2026, 10:22 a.m.