Triple
T27766861
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 客家人 |
E701622
|
entity |
| Predicate | 历史特征 |
P18777
|
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.
historicalCharacteristic
chosen
Indicates that an entity possesses a trait, feature, or quality that is rooted in or defined by its history or past events.
-
B.
strategicFeatureHistorical
Indicates that something has historically served as a strategic feature or asset within a broader plan, conflict, or competitive context.
-
C.
historicalBackground
Indicates that one entity provides contextual historical information or circumstances that help explain the origin, development, or significance of another entity.
-
D.
urbanHistoryFeature
Indicates a feature that plays a significant role in the historical development, events, or evolution of an urban area.
-
E.
historicalFocus
Indicates that something is primarily concerned with, centered on, or devoted to a particular historical period, event, or theme.
- 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_69ef6a52fa708190934a32308d2c92dc |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f637939be0819082653d4115cd1be1 |
completed | May 2, 2026, 5:42 p.m. |
| PD | Predicate disambiguation | batch_69f63188e7408190af8ce8b93d128c63 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 4:31 p.m.