Triple
T38165742
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | China–Vietnam relations |
E953136
|
entity |
| Predicate | tensionDriver |
P174943
|
FINISHED |
| Object | resource competition in the South China Sea |
—
|
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: resource competition in the South China Sea | Statement: [China–Vietnam relations, tensionDriver, resource competition in the South China Sea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tensionDriver Context triple: [China–Vietnam relations, tensionDriver, resource competition in the South China Sea]
-
A.
tensionMethod
Indicates the method or technique used to apply or maintain tension in a system or between components.
-
B.
tensionSource
chosen
Indicates that one entity is the origin or cause of tension affecting another entity or situation.
-
C.
hasTension
Indicates the presence of strain, stress, or conflict between entities in their relationship or interaction.
-
D.
tension
Indicates a state of strain, stress, or conflict existing between entities, often involving opposing forces, interests, or emotions.
-
E.
tensionFactor
Indicates the degree or intensity of tension present in the relationship or interaction between entities.
- 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_69f76f0b93c48190a117319ab3a9f282 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcb089a8f881909aa9e722babd43f7 |
completed | May 7, 2026, 3:32 p.m. |
| PD | Predicate disambiguation | batch_69fc45666c5c8190913bd632ac0e5b84 |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 3, 2026, 4:21 p.m.