Triple
T439487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South China Sea |
E10082
|
entity |
| Predicate | hasClaim |
P13068
|
FINISHED |
| Object | nine-dash line claim by China |
—
|
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: nine-dash line claim by China | Statement: [South China Sea, hasClaim, nine-dash line claim by China]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClaim Context triple: [South China Sea, hasClaim, nine-dash line claim by China]
-
A.
supportsClaim
Indicates that one entity provides evidence, reasoning, or backing that strengthens or validates the truth or credibility of another entity’s claim.
-
B.
hasNotableClaim
chosen
Indicates that an entity is associated with a significant, widely recognized statement, assertion, or claim.
-
C.
definesClaim
Indicates that one entity specifies or establishes the meaning, scope, or content of another entity’s claim.
-
D.
hasCollectiveRightClaim
Indicates that a group or collective entity asserts or holds a right or entitlement on behalf of its members.
-
E.
hasCredit
Indicates that an entity possesses or is assigned a credit, such as financial credit, academic credit, or acknowledgment for a contribution.
- 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_69a2e8465ef481909655c681b01e2986 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2ef2977888190a0590b2c1bd2f5da |
completed | Feb. 28, 2026, 1:35 p.m. |
| PD | Predicate disambiguation | batch_69a2eddcf50c8190bfa0d1f8ee9f604a |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:11 p.m.