Triple
T10113677
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nineteen Day Feast |
E218302
|
entity |
| Predicate | consultationTopic |
P85983
|
FINISHED |
| Object | community affairs |
—
|
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: community affairs | Statement: [Nineteen Day Feast, consultationTopic, community affairs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: consultationTopic Context triple: [Nineteen Day Feast, consultationTopic, community affairs]
-
A.
consultsOn
Indicates that one entity provides expert advice, guidance, or professional input to another entity regarding a specific subject, project, or decision.
-
B.
canDiscuss
Indicates that one entity is able or permitted to engage in a discussion or conversation with another entity.
-
C.
questionTopic
Indicates that a question is about, concerns, or is primarily focused on a particular topic or subject.
-
D.
planningTopic
chosen
Indicates that the subject is the topic, theme, or focus around which planning activities or plans are being organized or developed.
-
E.
consulted
Indicates that one entity sought advice, information, or guidance from another entity.
- 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_69ca83da93fc8190b54e44bc2b34857c |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cdd15ed28081909a812e0634799ef8 |
completed | April 2, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69cd4b9ed7e48190aa132ef8a69b49f9 |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:04 p.m.