Triple
T14503747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Angier, North Carolina |
E340207
|
entity |
| Predicate | hasCommunityEventType |
P14526
|
FINISHED |
| Object | seasonal festivals |
—
|
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: seasonal festivals | Statement: [Angier, North Carolina, hasCommunityEventType, seasonal festivals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommunityEventType Context triple: [Angier, North Carolina, hasCommunityEventType, seasonal festivals]
-
A.
hasCommunityType
Indicates that an entity is associated with or classified under a particular type or category of community.
-
B.
hasCommunityIn
Indicates that a community is present, active, or established within a specified location, platform, or context.
-
C.
hasCommunityGroup
Indicates that an entity is associated with, or belongs to, a specific community group.
-
D.
hasEventType
chosen
Indicates that an event is associated with, or classified under, a specific type or category of event.
-
E.
hasCommunityGroups
Indicates that an entity is associated with one or more organized community groups or organizations.
- 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_69d822d9c0408190b9a2b3643e58bb4d |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69de94e0f9048190a2d266cfa4f9dfb6 |
completed | April 14, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69de5c4ccba08190a988bfda0bc9f5cb |
completed | April 14, 2026, 3:25 p.m. |
Created at: April 10, 2026, 1:21 a.m.