Triple
T25929624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hopkinsville Goblins incident of 1955 |
E653400
|
entity |
| Predicate | numberOfWitnesses |
P109137
|
FINISHED |
| Object | approximately 11 |
—
|
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: approximately 11 | Statement: [Hopkinsville Goblins incident of 1955, numberOfWitnesses, approximately 11]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfWitnesses Context triple: [Hopkinsville Goblins incident of 1955, numberOfWitnesses, approximately 11]
-
A.
numberOfWitnessesHeard
Indicates the count of witnesses whose testimony or statements were heard in a given event or proceeding.
-
B.
witnessCount
chosen
Indicates the number of distinct witnesses associated with a particular event, action, or relationship.
-
C.
witnesses
Indicates that one entity observes an event, action, or situation involving another entity, typically as a bystander or observer.
-
D.
onlyWitnessOf
Indicates that one entity is the sole witness to an event, action, or situation involving another entity, with no other witnesses present.
-
E.
notableWitness
Indicates that one entity is a significant or prominent witness to an event, action, or situation involving another entity.
- 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_69e7ab3eb9b881909c1390690551f868 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69fd2839880c819099a7a89783f2270e |
completed | May 8, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69fd23dc5da48190ae8ba08947d34956 |
completed | May 7, 2026, 11:44 p.m. |
Created at: April 22, 2026, 8:36 a.m.