Triple
T25428437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 啟臣 |
E637183
|
entity |
| Predicate | bearerPositionHeld |
P8
|
FINISHED |
| Object | member of the Legislative Yuan |
—
|
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: member of the Legislative Yuan | Statement: [啟臣, bearerPositionHeld, member of the Legislative Yuan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bearerPositionHeld Context triple: [啟臣, bearerPositionHeld, member of the Legislative Yuan]
-
A.
bearerPosition
Indicates the spatial or positional relationship of a bearer (holder or carrier) relative to the item or entity it bears.
-
B.
positionHeld
chosen
Indicates that an entity occupies or has occupied a specific role, job, office, or position within an organization or context.
-
C.
positionHeldUnder
Indicates that one entity holds or held a specific position, office, or role under the authority, administration, or jurisdiction of another entity.
-
D.
bearerStance
Indicates the attitude, position, or viewpoint that the bearer holds toward a referenced subject or issue.
-
E.
canAlsoHoldPosition
Indicates that an entity, in addition to its current role or position, is capable of occupying or being assigned another specified position.
- 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_69e75db58a1c8190891b9ff7c2f8414e |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f60c3b09488190ade1b69ff7f0df0e |
completed | May 2, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f60b8461ac81908c5bd3d73eed59f4 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 21, 2026, 1:58 p.m.