Triple
T272910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apple Harvest Festival |
E5675
|
entity |
| Predicate | hasSocialFunction |
P3795
|
FINISHED |
| Object | community gathering |
—
|
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 gathering | Statement: [Apple Harvest Festival, hasSocialFunction, community gathering]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSocialFunction Context triple: [Apple Harvest Festival, hasSocialFunction, community gathering]
-
A.
hasPrimaryFunction
Indicates that one entity serves as the main or principal function or role of another entity.
-
B.
hasMean
Indicates that one entity possesses, exhibits, or is characterized by a particular mean value or average.
-
C.
secondaryFunction
Indicates that an entity has an additional, supporting role or purpose beyond its primary function.
-
D.
hasCulturalRole
chosen
Indicates that an entity fulfills or is assigned a specific function, position, or significance within a cultural, social, or traditional context.
-
E.
notFunction
Indicates that the specified entity does not serve as a function or is not used in a functional role within the given context.
- 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.