Triple
T29387769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Twenty-One Demands |
E745296
|
entity |
| Predicate | group2Subject |
P61730
|
FINISHED |
| Object | South Manchuria and Eastern Inner Mongolia |
—
|
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: South Manchuria and Eastern Inner Mongolia | Statement: [Twenty-One Demands, group2Subject, South Manchuria and Eastern Inner Mongolia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: group2Subject Context triple: [Twenty-One Demands, group2Subject, South Manchuria and Eastern Inner Mongolia]
-
A.
subjectGroup
Indicates that an entity functions as a group or collection that the subject belongs to or is categorized under.
-
B.
groups
Indicates that one entity organizes, clusters, or associates multiple entities together as members of a collective set or category.
-
C.
byGroup
Indicates that something is organized, classified, or associated according to a particular group or grouping.
-
D.
subgroupCategory
Indicates that one category functions as a more specific subgroup within the scope of another, broader category.
-
E.
participantGroup
chosen
Indicates a relationship in which a set or group of entities jointly participate in a common event, activity, or interaction.
- 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_69f0a79cfd5481909b4dde750cb8d2c6 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f676f968d08190a4adba0439b438c9 |
completed | May 2, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69f675ff62c48190a634bbb8896973b9 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 28, 2026, 2:40 p.m.