Triple
T339755
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grassy Knoll |
E6806
|
entity |
| Predicate | visitedFor |
P11614
|
FINISHED |
| Object | historical significance |
—
|
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: historical significance | Statement: [Grassy Knoll, visitedFor, historical significance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: visitedFor Context triple: [Grassy Knoll, visitedFor, historical significance]
-
A.
visitedBy
Indicates that a location or entity is the destination or target of a visit performed by another entity.
-
B.
explored
Indicates that an entity has traveled through, examined, or investigated another entity or area, typically to discover or learn more about it.
-
C.
frequentlyVisitedBy
Indicates that an entity is regularly or often visited by another entity.
-
D.
wentTo
Indicates that one entity traveled or moved from its original location to another specified place.
-
E.
usedBefore
Indicates that one entity was utilized or applied prior to the use or occurrence of another entity.
- F. None of above. chosen
Provenance (4 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_69a2e7951ba08190960e90823b5078f3 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2eae4fcc08190bd4c2bf0149c8b50 |
completed | Feb. 28, 2026, 1:17 p.m. |
| PD | Predicate disambiguation | batch_69a2e95067e88190a914a1c1d0283dfc |
completed | Feb. 28, 2026, 1:10 p.m. |
| PDg | Predicate description generation | batch_69a2ea09a5e881908b313cb37409a4f9 |
completed | Feb. 28, 2026, 1:13 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.