Triple
T30570925
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unnamed narrator of The Gold-Bug |
E778118
|
entity |
| Predicate | relationshipToEvents |
P85529
|
FINISHED |
| Object | eyewitness |
—
|
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: eyewitness | Statement: [Unnamed narrator of The Gold-Bug, relationshipToEvents, eyewitness]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToEvents Context triple: [Unnamed narrator of The Gold-Bug, relationshipToEvents, eyewitness]
-
A.
relationshipToEvent
chosen
Indicates the specific way an entity is connected or related to a particular event.
-
B.
relativeInvolvedInEvent
Indicates that a person’s relative participates in, is affected by, or is otherwise involved in a particular event.
-
C.
individualEvents
Indicates that the subject is associated with one or more distinct, separately identifiable events rather than a single aggregated or continuous occurrence.
-
D.
associatedWithCorporateEvent
Indicates that an entity has a connection or involvement with a specific corporate event.
-
E.
relatedFestivalType
Indicates that one festival is associated with another through a shared or corresponding festival type or category.
- 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_69f2249f8c148190ae7eb3912cde112a |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a032616547c8190bc877202e43403eb |
completed | May 12, 2026, 1:07 p.m. |
| PD | Predicate disambiguation | batch_6a0325246abc819088e16a7fbadf40c5 |
completed | May 12, 2026, 1:03 p.m. |
Created at: April 29, 2026, 8:22 p.m.