Triple
T33651275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STDM |
E862105
|
entity |
| Predicate | hasPrimaryActivityLocation |
P110976
|
FINISHED |
| Object | Macau SAR, China |
E7092
|
NE 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: Macau SAR, China | Statement: [STDM, hasPrimaryActivityLocation, Macau SAR, China]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryActivityLocation Context triple: [STDM, hasPrimaryActivityLocation, Macau SAR, China]
-
A.
hasPrimaryLocationSetting
Indicates that an entity is associated with its main or default geographic or contextual location.
-
B.
hasPrimaryBusinessLocation
chosen
Indicates that an entity’s main or principal place of business is located at a specified location.
-
C.
hasPrimaryAssetLocation
Indicates that an entity’s main or principal asset is located at a specified place or facility.
-
D.
hasActLocation
Indicates that an action or event occurs at, or is associated with, a specific location.
-
E.
hasMainLocationType
Indicates that an entity is associated with a primary or predominant type of location that characterizes where it is mainly situated or operates.
- F. None of above.
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_69f349840ba881908e3bfce536aeb92b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a01b841f5508190832bba00cf795bad |
completed | May 11, 2026, 11:06 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a36822364208190adb4e9ce6a3524b0 |
completed | June 20, 2026, 12:05 p.m. |
| PD | Predicate disambiguation | batch_6a01b59541fc8190a9b13a55327c4aa1 |
completed | May 11, 2026, 10:55 a.m. |
Created at: May 1, 2026, 1:42 a.m.