Triple
T37542634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Embassy of China in Vietnam |
E933368
|
entity |
| Predicate | sectorInvolvedIn |
P100108
|
FINISHED |
| Object | politics |
—
|
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: politics | Statement: [Embassy of China in Vietnam, sectorInvolvedIn, politics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sectorInvolvedIn Context triple: [Embassy of China in Vietnam, sectorInvolvedIn, politics]
-
A.
sectorRepresented
Indicates that an entity serves as a representative or proxy for a particular sector (such as an industry, domain, or market segment).
-
B.
sectorOfOperation
chosen
Indicates the industry, domain, or field within which an entity conducts its primary activities or operations.
-
C.
sectorInspected
Indicates that a particular sector or area has been examined or checked, typically for compliance, safety, or condition.
-
D.
ownerSector
Indicates the sector or industry category to which the owner of an entity belongs.
-
E.
sectorGoverned
Indicates that a particular sector or domain is under the authority, control, or regulatory oversight of a specified governing entity.
- 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_69f76ec999288190ae26ec7b6aea7046 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba5eec0448190a5e6f0c43fdcd0e3 |
completed | May 6, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69fba34edd548190bfa980e6e16e0a88 |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.