Triple
T27968294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 畲族 |
E704784
|
entity |
| Predicate | 祖先传说 |
P40749
|
FINISHED |
| Object | 盘瓠 |
—
|
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: 盘瓠 | Statement: [畲族, 祖先传说, 盘瓠]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 祖先传说 Context triple: [畲族, 祖先传说, 盘瓠]
-
A.
originMyth
chosen
Indicates the traditional myth or legendary narrative that explains the beginnings or creation of a people, place, institution, or phenomenon.
-
B.
mythologicalGeneration
Indicates a generational relationship in mythology, where one mythological being or group descends from or follows another in a lineage or succession.
-
C.
開基
Indicates the act of founding or establishing something for the first time, such as initiating a lineage, enterprise, or domain.
-
D.
originStoryIncludes
Indicates that an entity’s origin story contains, involves, or features the referenced element as a component or part of that backstory.
-
E.
mythologicalContent
Indicates that the subject contains, references, or is associated with myths, mythological narratives, or myth-based elements.
- 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.