Triple
T27968286
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 畲族 |
E704784
|
entity |
| Predicate | 传统婚俗特点 |
P38203
|
FINISHED |
| Object | 歌堂对唱 |
—
|
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: 歌堂对唱 | Statement: [畲族, 传统婚俗特点, 歌堂对唱]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 传统婚俗特点 Context triple: [畲族, 传统婚俗特点, 歌堂对唱]
-
A.
traditionCharacteristic
Indicates that a particular quality, feature, or attribute is characteristic of, or typically associated with, a given tradition.
-
B.
culturalTradition
Indicates a relationship where certain practices, beliefs, or customs are recognized as part of a shared cultural heritage passed down within a group or society.
-
C.
cultureCharacteristic
Indicates that a particular trait, practice, or feature is a defining characteristic of a given culture.
-
D.
marriageCustom
chosen
Indicates a culturally recognized set of practices, rules, or traditions that govern how marriages are formed, conducted, or maintained between individuals or groups.
-
E.
languageTraditions
Indicates that there is a relationship between entities involving the customs, practices, and conventions associated with the use, preservation, or transmission of a particular language.
- 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_69ef841061e48190b5570f9562f7434d |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f63b3337748190ae03ce1742a31d22 |
completed | May 2, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69f63710d17c819084cfe96e6df334fd |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 7:36 p.m.