Triple
T33079649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lieyu Island |
E846471
|
entity |
| Predicate | sawConflict |
P175780
|
FINISHED |
| Object | Second Taiwan Strait Crisis |
—
|
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: Second Taiwan Strait Crisis | Statement: [Lieyu Island, sawConflict, Second Taiwan Strait Crisis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sawConflict Context triple: [Lieyu Island, sawConflict, Second Taiwan Strait Crisis]
-
A.
subConflict
Indicates that one conflict is a component, phase, or subordinate part of a larger overarching conflict.
-
B.
reportedConflict
Indicates that one party has formally reported the existence of a conflict involving another party or situation.
-
C.
ledToConflict
Indicates that one event, action, or condition caused or significantly contributed to the emergence or escalation of a conflict between parties.
-
D.
wonConflict
Indicates that one entity has prevailed over another in a conflict, contest, or struggle.
-
E.
supportedConflict
Indicates that one party provided assistance, resources, or endorsement to a side involved in a conflict or dispute.
- 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_69f34954d46c8190a04a159cc5f99efd |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d74b20a48190900dda1014cc13a8 |
completed | May 3, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69f6d27120988190aacec621cf2bf0e8 |
completed | May 3, 2026, 4:43 a.m. |
| PDg | Predicate description generation | batch_69f6d6a482fc8190b526291cd99b8696 |
completed | May 3, 2026, 5:01 a.m. |
Created at: May 1, 2026, 1:25 a.m.