Triple
T28264331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WMT |
E712659
|
entity |
| Predicate | hasSecuritySubtype |
P193651
|
FINISHED |
| Object | Common stock |
—
|
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: Common stock | Statement: [WMT, hasSecuritySubtype, Common stock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSecuritySubtype Context triple: [WMT, hasSecuritySubtype, Common stock]
-
A.
hasSecurityCategory
Indicates that an entity is associated with a particular security classification or category defining its protection or access level.
-
B.
hasSecurityDimension
Indicates that something possesses or is associated with a particular aspect or dimension of security.
-
C.
hasSecurityPresence
Indicates that some form of security personnel, system, or measures are present at or associated with an entity or location.
-
D.
hasSecurityFunction
Indicates that an entity performs, provides, or is responsible for a security-related role, protection mechanism, or safeguarding function for another entity or system.
-
E.
hasSecurityDimensionWith
Indicates that one entity is associated with a specific security-related aspect, characteristic, or dimension of another entity.
- F. None of above. chosen
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_69efb5216c6881908020dce4aea65381 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69fd4f39b5008190b83b3227ce22c509 |
completed | May 8, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69fd4df17c548190a4e2a6fea70f7e10 |
completed | May 8, 2026, 2:44 a.m. |
| PDg | Predicate description generation | batch_69fd4f38728c8190b3271abc80882cfb |
completed | May 8, 2026, 2:49 a.m. |
Created at: April 27, 2026, 11:13 p.m.