Triple
T26699012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South China Sea maritime claims |
E673099
|
entity |
| Predicate | tensionLevel |
P61198
|
FINISHED |
| Object | high |
—
|
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: high | Statement: [South China Sea maritime claims, tensionLevel, high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tensionLevel Context triple: [South China Sea maritime claims, tensionLevel, high]
-
A.
tension
Indicates a state of strain, stress, or conflict existing between entities, often involving opposing forces, interests, or emotions.
-
B.
hasTension
chosen
Indicates the presence of strain, stress, or conflict between entities in their relationship or interaction.
-
C.
hasTypeOfTension
Indicates that one entity is associated with, or characterized by, a specific kind or category of tension.
-
D.
languageTension
Indicates a relationship where differing languages or language use create conflict, strain, or friction between entities.
-
E.
tensionMethod
Indicates the method or technique used to apply or maintain tension in a system or between components.
- 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_69eecda2b49c8190a6c481cfc4c07954 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f6177e2870819092bd441b95a21223 |
completed | May 2, 2026, 3:25 p.m. |
| PD | Predicate disambiguation | batch_69f60b8bb0d08190ab5a9a2a8847c6f4 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 3:30 a.m.