Triple
T32113614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guard of the Citadel |
E820179
|
entity |
| Predicate | guardedPerson |
P97703
|
FINISHED |
| Object | Steward of Gondor |
—
|
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: Steward of Gondor | Statement: [Guard of the Citadel, guardedPerson, Steward of Gondor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: guardedPerson Context triple: [Guard of the Citadel, guardedPerson, Steward of Gondor]
-
A.
guard
chosen
Indicates that one entity protects, watches over, or defends another entity or resource from harm, intrusion, or unauthorized access.
-
B.
guardedIn
Indicates that one entity is protected or kept under watch within the bounds or premises of another entity.
-
C.
guardedAs
Indicates that one entity is protected, watched over, or kept secure in the role or capacity specified by another entity.
-
D.
guardedEntranceTo
Indicates that one entity serves as a protective or controlling barrier for access to another entity’s entrance.
-
E.
guardedPassage
Indicates that access through a passage is controlled or protected by a guard or security presence.
- 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_69f3490209c881908ec0241476715f15 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c1bb5f248190834161b5a6ba1ece |
completed | May 3, 2026, 3:32 a.m. |
| PD | Predicate disambiguation | batch_69f6bd25bed08190befcabd3a41ffadf |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 12:27 a.m.