Triple
T272920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chili Cook-Off |
E5676
|
entity |
| Predicate | involvesParticipant |
P2434
|
FINISHED |
| Object | local residents |
—
|
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: local residents | Statement: [Chili Cook-Off, involvesParticipant, local residents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvesParticipant Context triple: [Chili Cook-Off, involvesParticipant, local residents]
-
A.
determinesParticipantIn
Indicates that one entity has the authority or role to decide or specify which other entity (or entities) will participate in a given event, activity, or process.
-
B.
notableParticipant
Indicates that an entity plays a significant or distinguished role as a participant in an event, activity, or context.
-
C.
participant
Indicates that an entity takes part in, is involved in, or plays a role within a specified event, activity, or process.
-
D.
participation
Indicates that an entity takes part in, contributes to, or is involved in a shared activity, event, or process with others.
-
E.
hasParticipants
chosen
Indicates that an event, activity, or situation involves one or more entities as participants in it.
- 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_69a25853594c8190b05ec3a586ec88bf |
completed | Feb. 28, 2026, 2:52 a.m. |
| NER | Named-entity recognition | batch_69a25dcf667c8190a7b8630fe67b9a90 |
completed | Feb. 28, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69a25b7345c4819086c21710864a1b42 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:57 a.m.