Triple
T38566454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Minas Tirith of Finrod |
E928231
|
entity |
| Predicate | regionGuarded |
P132993
|
FINISHED |
| Object | northern Beleriand |
—
|
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: northern Beleriand | Statement: [Minas Tirith of Finrod, regionGuarded, northern Beleriand]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionGuarded Context triple: [Minas Tirith of Finrod, regionGuarded, northern Beleriand]
-
A.
guardedRegion
Indicates that a region is protected or watched over by some guarding entity or mechanism.
-
B.
isProtectedAreaOf
Indicates that a designated protected area (such as a park or reserve) is established to conserve and manage a specific geographic region or natural feature.
-
C.
protectsArea
chosen
Indicates that one entity serves to guard, defend, or preserve a particular area or region from harm or intrusion.
-
D.
stateProtectedBy
Indicates that a state is defended or safeguarded by a specified protecting entity (such as another state, organization, or authority).
-
E.
regionLocking
Indicates that access to or use of something is restricted based on the geographic region of the user or device.
- 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_69f76eb8d1808190a588af29d8b266d6 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a00a15604fc8190b1c280794960f3a4 |
completed | May 10, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_6a00a0f7e77881909ac85755ab0e6329 |
completed | May 10, 2026, 3:15 p.m. |
Created at: May 3, 2026, 4:32 p.m.