Triple
T24942959
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Memorial Fence |
E623508
|
entity |
| Predicate | hasVisitorInteraction |
P157393
|
FINISHED |
| Object | visitors may read existing tributes |
—
|
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: visitors may read existing tributes | Statement: [Memorial Fence, hasVisitorInteraction, visitors may read existing tributes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVisitorInteraction Context triple: [Memorial Fence, hasVisitorInteraction, visitors may read existing tributes]
-
A.
hasInteraction
Indicates that there is some form of interaction or mutual action occurring between the related entities.
-
B.
hasVisitorInterest
Indicates that an entity has a particular interest, preference, or attraction toward visiting another entity or location.
-
C.
hasVisitorActivities
chosen
Indicates that a place or entity offers or is associated with specific activities available for visitors to engage in.
-
D.
hasVisitation
Indicates that one entity visits, or is allowed or scheduled to visit, another entity or location.
-
E.
hasVisitorType
Indicates the type or category of visitor associated with an entity (e.g., guest, customer, tourist, patient).
- 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_69e2fac6b5a48190a1c38857f00915a9 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f5f6baf2d48190a6a4cd6501be87d2 |
completed | May 2, 2026, 1:06 p.m. |
| PD | Predicate disambiguation | batch_69f5afd5baac8190bb8ed576813c8591 |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 18, 2026, 5:31 a.m.