Triple
T10110361
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | All-China Youth Federation |
E218222
|
entity |
| Predicate | roleInCPPCC |
P11005
|
FINISHED |
| Object | mass organization sector representative |
—
|
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: mass organization sector representative | Statement: [All-China Youth Federation, roleInCPPCC, mass organization sector representative]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInCPPCC Context triple: [All-China Youth Federation, roleInCPPCC, mass organization sector representative]
-
A.
typeOfOrganizationChaired
Indicates the specific kind or category of organization over which an entity serves as chair or leader.
-
B.
intraPartyRole
Indicates a role or function that an entity holds within a specific political party or internal party structure.
-
C.
coChairpersonOf
Indicates that a person serves jointly with one or more others as the chairperson of a group, organization, or committee.
-
D.
roleInCouncil
chosen
Indicates that an entity holds a specific position or function within a council or governing body.
-
E.
hasOrganizationalRole
Indicates that an entity holds a specific role, position, or function within an organization.
- 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_69ca83da93fc8190b54e44bc2b34857c |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cdd0cf39908190bba679ace095eefc |
completed | April 2, 2026, 2:13 a.m. |
| PD | Predicate disambiguation | batch_69cd4b9ed7e48190aa132ef8a69b49f9 |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:03 p.m.