Triple
T8681713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ba Lu Jun |
E206052
|
entity |
| Predicate | secondaryOpponent |
P84462
|
FINISHED |
| Object | collaborationist Chinese forces |
—
|
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: collaborationist Chinese forces | Statement: [Ba Lu Jun, secondaryOpponent, collaborationist Chinese forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondaryOpponent Context triple: [Ba Lu Jun, secondaryOpponent, collaborationist Chinese forces]
-
A.
secondaryCompetition
Indicates that one entity participates in or is involved with a secondary or subordinate competition relative to a primary one.
-
B.
opponentInCase
Indicates that two parties are on opposing sides in the same legal case or proceeding.
-
C.
secondRunnerUp
Indicates that one entity finished in third place in a competition or ranking relative to the others.
-
D.
secondaryTo
Indicates that one condition, event, or factor occurs as a consequence of, or is caused by, another primary condition, event, or factor.
-
E.
secondaryStadium
Indicates that an entity serves as an additional or backup stadium associated with another primary stadium or team.
- F. None of above. chosen
Provenance (4 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_69ca835379688190aa06b9d98e684d58 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc4ae82e508190b0243328e98fcb1d |
completed | March 31, 2026, 10:30 p.m. |
| PD | Predicate disambiguation | batch_69cc4567b5c881908d9ec5dcfc783fac |
completed | March 31, 2026, 10:06 p.m. |
| PDg | Predicate description generation | batch_69cc4ae517108190a71a86349815f4ce |
completed | March 31, 2026, 10:29 p.m. |
Created at: March 30, 2026, 6:32 p.m.