Triple
T29387770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Twenty-One Demands |
E745296
|
entity |
| Predicate | group3Subject |
P169311
|
FINISHED |
| Object | Hanyeping mining and metallurgical complex |
E414738
|
NE 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: Hanyeping mining and metallurgical complex | Statement: [Twenty-One Demands, group3Subject, Hanyeping mining and metallurgical complex]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: group3Subject Context triple: [Twenty-One Demands, group3Subject, Hanyeping mining and metallurgical complex]
-
A.
subjectGroup
Indicates that an entity functions as a group or collection that the subject belongs to or is categorized under.
-
B.
schoolSubject
Indicates that an entity is an academic subject taught, studied, or associated with a school or educational program.
-
C.
subjectType
Indicates the classification or category that defines what kind of entity the subject is.
-
D.
schoolSubjectContext
Indicates that an entity is being considered specifically in the context of a school subject or academic discipline.
-
E.
book3Subject
Indicates that an entity serves as the third subject or topic discussed or treated in a particular book.
- F. None of above. chosen
Provenance (5 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_69f0a79cfd5481909b4dde750cb8d2c6 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f67de7792c81909b5e4e812d143624 |
completed | May 2, 2026, 10:42 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a25c10fccf88190bc8cd3ece9c38c84 |
completed | June 7, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69f678ce54b081908c26edfd49e39c60 |
completed | May 2, 2026, 10:21 p.m. |
| PDg | Predicate description generation | batch_69f67d31cc60819084f64bd056e1ea4d |
completed | May 2, 2026, 10:39 p.m. |
Created at: April 28, 2026, 2:40 p.m.