Triple
T38564503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maonan people |
E928177
|
entity |
| Predicate | hasDistinctFestival |
P146916
|
FINISHED |
| Object | Maonan New Year |
—
|
NE NERFINISHED |
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: Maonan New Year | Statement: [Maonan people, hasDistinctFestival, Maonan New Year]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDistinctFestival Context triple: [Maonan people, hasDistinctFestival, Maonan New Year]
-
A.
hasFestival
Indicates that a location, community, or entity hosts or holds a festival or celebratory event.
-
B.
hasKeyFestival
chosen
Indicates that an entity is associated with a primary or central festival that is especially significant to it.
-
C.
hasFestivalGenre
Indicates that a festival is associated with or categorized under a particular genre.
-
D.
hasFestivalFrequency
Indicates how often a festival or recurring celebratory event takes place within a given time period.
-
E.
hasFestivalConnection
Indicates a relationship in which two entities are connected through a festival, such as by participation, organization, sponsorship, or association with that event.
- 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_69f76eb8d1808190a588af29d8b266d6 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ffc7b4c7f88190b6357a44e7f0940f |
completed | May 9, 2026, 11:48 p.m. |
| PD | Predicate disambiguation | batch_69ffc755f09c8190995ca00d97336988 |
completed | May 9, 2026, 11:46 p.m. |
Created at: May 3, 2026, 4:32 p.m.