Triple
T38448774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hollin Gate |
E906709
|
entity |
| Predicate | passwordInStory |
P180758
|
FINISHED |
| Object | mellon |
—
|
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: mellon | Statement: [Hollin Gate, passwordInStory, mellon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: passwordInStory Context triple: [Hollin Gate, passwordInStory, mellon]
-
A.
passwordProtectedBy
Indicates that access to an entity is restricted and can only be obtained by providing a specific password associated with another entity.
-
B.
protagonistSecret
Indicates that one entity is the main character who possesses or is associated with a hidden fact, identity, or piece of information unknown to others.
-
C.
inStoryObtainedBy
Indicates that something is obtained by an entity within the context of a specific story or narrative.
-
D.
fieldInStory
chosen
Indicates that a particular field or attribute appears within, or is defined as part of, a given story.
-
E.
guardedByInFiction
Indicates that one fictional entity is protected or watched over by another within a narrative context.
- 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_69f76e72878c8190a692836c8b01b58b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcdaa36f90819093f8661969990c7d |
completed | May 7, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fefc588190b063d7ea1ec87b07 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:31 p.m.