Triple
T36550936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stoor |
E901254
|
entity |
| Predicate | originallyLivedIn |
P38603
|
FINISHED |
| Object | vales of the Anduin |
E909919
|
NE 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: vales of the Anduin | Statement: [Stoor, originallyLivedIn, vales of the Anduin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originallyLivedIn Context triple: [Stoor, originallyLivedIn, vales of the Anduin]
-
A.
countyOfOrigin
Indicates the county from which an entity originally comes or was first produced.
-
B.
originalHomeland
chosen
Indicates the place or region that is considered the ancestral or earliest homeland of an entity.
-
C.
residedOn
Indicates that an entity lived or had its primary dwelling at a specific location during a certain period.
-
D.
allegedBirthRegion
Indicates the region where an entity is claimed or reported to have been born, without asserting that this birthplace is verified as fact.
-
E.
placeOfBirth
Indicates the location where a person or other entity was born.
- F. None of above.
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_69f76e61217081908b79d610fe67b013 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a39f90809988190952ff4e7bc30f45e |
completed | June 23, 2026, 3:10 a.m. |
| PD | Predicate disambiguation | batch_6a037a0bf4b88190bdcfae9a14b51f0a |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:11 p.m.