Triple
T5607275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OTC:NSRGY |
E147263
|
entity |
| Predicate | hasIssuerPrimaryBusiness |
P64615
|
FINISHED |
| Object | Food and beverage products |
—
|
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: Food and beverage products | Statement: [OTC:NSRGY, hasIssuerPrimaryBusiness, Food and beverage products]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIssuerPrimaryBusiness Context triple: [OTC:NSRGY, hasIssuerPrimaryBusiness, Food and beverage products]
-
A.
hasIssuerCode
Indicates that an entity is associated with a specific issuer’s identifying code.
-
B.
headquartersOfIssuer
Indicates the location that serves as the main headquarters of the issuing entity.
-
C.
issuerOwnsBusinessesIn
Indicates that the issuer owns one or more business entities that are located or operate within the specified place.
-
D.
isIssuedFor
Indicates that something (such as a document, order, or item) has been formally created, authorized, or provided for a specific purpose, recipient, or use.
-
E.
hasPrimaryInstitutionType
Indicates that an entity’s main or principal institutional classification or category is of a specified type.
- 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_69c0090500f881908374285baf0ac46f |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c020fbb8748190841e5e09db3feef1 |
completed | March 22, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69c01b1b3c98819080687d18ab10a914 |
completed | March 22, 2026, 4:38 p.m. |
| PDg | Predicate description generation | batch_69c01f0684908190ae2d14f0bd2ab892 |
completed | March 22, 2026, 4:55 p.m. |
Created at: March 22, 2026, 3:39 p.m.