Triple
T30633040
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tol-in-Gaurhoth |
E779760
|
entity |
| Predicate | guardedPass |
P63041
|
FINISHED |
| Object | Pass of Sirion |
—
|
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: Pass of Sirion | Statement: [Tol-in-Gaurhoth, guardedPass, Pass of Sirion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: guardedPass Context triple: [Tol-in-Gaurhoth, guardedPass, Pass of Sirion]
-
A.
guardedPassage
chosen
Indicates that access through a passage is controlled or protected by a guard or security presence.
-
B.
guardedAs
Indicates that one entity is protected, watched over, or kept secure in the role or capacity specified by another entity.
-
C.
guardedIn
Indicates that one entity is protected or kept under watch within the bounds or premises of another entity.
-
D.
guardedSecretBy
Indicates that a secret is being protected or kept confidential by a specific entity.
-
E.
protectedAs
Indicates that one entity is safeguarded, preserved, or kept safe by another entity or under a specified protective status or mechanism.
- 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_69f224a431548190a44ad9d088dbf91f |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ed5d008190831cf8e44cce28af |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 29, 2026, 8:28 p.m.