Triple
T32920776
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Weibo Corporation |
E842136
|
entity |
| Predicate | securityIdentifier |
P3732
|
FINISHED |
| Object | NASDAQ:WB |
—
|
NE NERFINISHED |
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: NASDAQ:WB | Statement: [Weibo Corporation, securityIdentifier, NASDAQ:WB]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: securityIdentifier Context triple: [Weibo Corporation, securityIdentifier, NASDAQ:WB]
-
A.
securityModelIdentifier
Indicates the specific security model or framework under which an entity, interaction, or policy is defined or governed.
-
B.
subjectIdentity
Indicates that two or more references correspond to the same underlying entity or individual identity.
-
C.
securityRole
Indicates that an entity holds a specific security-related role, permission level, or access profile within a system or context.
-
D.
identitySymbol
Indicates that one entity serves as the symbolic representation or signifier of another entity’s identity.
-
E.
identifierFor
chosen
Indicates that one entity serves as a unique identifying label or code for another 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_69f3494779388190a5d3e97f92278be2 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fb3425666081908916fcbf3b5dd907 |
completed | May 6, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69fb2f5f3164819099429c2cc3d24e01 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 1, 2026, 1:19 a.m.