Triple
T26913446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Three Noes policy toward mainland China |
E677453
|
entity |
| Predicate | leaderDuringPolicy |
P4208
|
FINISHED |
| Object | Chiang Ching-kuo |
—
|
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: Chiang Ching-kuo | Statement: [Three Noes policy toward mainland China, leaderDuringPolicy, Chiang Ching-kuo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leaderDuringPolicy Context triple: [Three Noes policy toward mainland China, leaderDuringPolicy, Chiang Ching-kuo]
-
A.
leaderDuring
chosen
Indicates that one entity serves as the leader of another entity during a specified time period.
-
B.
leaderSince
Indicates that an entity has held a leadership role over another entity starting from a specified point in time.
-
C.
leaderIsUsually
Indicates that an entity typically serves as the leader in relation to another entity or within a given context.
-
D.
leaderFrom
Indicates that an entity serves or has served as a leader originating from, representing, or associated with a specified place or organization.
-
E.
leader2
Indicates that one entity serves as a leader, chief, or primary authority figure in relation to another entity.
- 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_69eee9bcef1c8190be88586bb902bb9b |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f6247480cc8190a887eedaeb94615c |
completed | May 2, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69f623a7539c8190b71797f583da9f63 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 6:03 a.m.