Triple
T5478705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | US75513E1010 |
E123418
|
entity |
| Predicate | assignedToSecurityType |
P63995
|
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: [US75513E1010, assignedToSecurityType, common stock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: assignedToSecurityType Context triple: [US75513E1010, assignedToSecurityType, common stock]
-
A.
assignedUnder
Indicates that one entity has been given responsibility, duty, or authority to act within the scope, supervision, or framework defined by another entity.
-
B.
assignedToTerritoryType
Indicates that an entity has been allocated or linked to a specific type of territory within a defined territorial classification system.
-
C.
assignedToIssuer
Indicates that a responsibility, task, or item has been allocated or designated to the issuer.
-
D.
assignedInStandard
Indicates that something is allocated or designated within a defined standard, specification, or normative framework.
-
E.
hasSecurityCategory
Indicates that an entity is associated with a particular security classification or category defining its protection or access level.
- 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_69bd4648883481909e9775d43300c5fa |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd9247a16c8190ac5a02534da48853 |
completed | March 20, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69bd91a58c448190904964a439045e05 |
completed | March 20, 2026, 6:27 p.m. |
| PDg | Predicate description generation | batch_69bd9214b8488190979112c7615f359a |
completed | March 20, 2026, 6:29 p.m. |
Created at: March 20, 2026, 2:09 p.m.