Triple
T37036385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Argonath |
E916647
|
entity |
| Predicate | partOfSetting |
P15599
|
FINISHED |
| Object | Gondor’s northern frontier |
—
|
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: Gondor’s northern frontier | Statement: [Argonath, partOfSetting, Gondor’s northern frontier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfSetting Context triple: [Argonath, partOfSetting, Gondor’s northern frontier]
-
A.
partialSettingOf
Indicates that one entity establishes or configures only some aspects or components of another entity, rather than defining it completely.
-
B.
partOneSetting
Indicates that one entity specifies or defines the setting or context for the first part of another entity (such as a work, event, or process).
-
C.
coversSetting
Indicates that one entity includes or addresses a particular setting or context within its scope.
-
D.
setting
Indicates the place, time, or context in which an event, action, or interaction occurs.
-
E.
usedAsSettingFor
chosen
Indicates that one entity serves as the backdrop, location, or environment in which another entity (such as an event, story, or activity) takes place.
- 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_69f76e93ec4c8190be81cf87354d9155 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a013e23698c81909a32d371b6f158d0 |
completed | May 11, 2026, 2:25 a.m. |
| PD | Predicate disambiguation | batch_6a013db04b108190985897aa6e95b4ec |
completed | May 11, 2026, 2:23 a.m. |
Created at: May 3, 2026, 4:14 p.m.