Triple
T13186466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piedmont Community Hall |
E313867
|
entity |
| Predicate | accessibleForEventType |
P108950
|
FINISHED |
| Object | private events |
—
|
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: private events | Statement: [Piedmont Community Hall, accessibleForEventType, private events]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accessibleForEventType Context triple: [Piedmont Community Hall, accessibleForEventType, private events]
-
A.
appearsAtEventType
Indicates that an entity is present or participates in an event of a specified type.
-
B.
refersToEventType
Indicates that one entity references or is associated with a specific type or category of event.
-
C.
accessibleOn
Indicates that one entity can be reached, used, or obtained through another entity (such as a platform, device, or medium).
-
D.
accessibleAs
Indicates that one entity can be reached, used, or obtained through another entity, often as an alternative form, route, or representation.
-
E.
accessibleFrom
Indicates that one entity can be reached, entered, or used starting from another entity, typically without obstruction.
- 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_69d806ae1e08819090d95bfe1538cc17 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf054f88190b05ced98d5a22a62 |
completed | April 10, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69d98bc6bc108190b5a6a265bf6e9fd4 |
completed | April 10, 2026, 11:46 p.m. |
| PDg | Predicate description generation | batch_69d98ceeb22c8190a6be666031d9e5a4 |
completed | April 10, 2026, 11:51 p.m. |
Created at: April 9, 2026, 9:15 p.m.