Triple
T3050532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | US20030N1019 |
E83557
|
entity |
| Predicate | financialInstrumentCategory |
P4851
|
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: [US20030N1019, financialInstrumentCategory, common stock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: financialInstrumentCategory Context triple: [US20030N1019, financialInstrumentCategory, common stock]
-
A.
fundingInstrument
Indicates that one entity serves as the financial source, mechanism, or tool used to provide funding for another entity or activity.
-
B.
investmentType
chosen
Indicates the specific category or nature of an investment associated with an entity or transaction.
-
C.
cardType
Indicates the classification or category assigned to a card within a given system or context.
-
D.
tradeInstrument
Indicates a relationship where one entity is used as a financial or commercial instrument in a trade or transaction involving another entity.
-
E.
notableAssetClass
Indicates that an entity is significantly associated with, or recognized for, a particular class of assets.
- 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_69ad8b24924c8190a9bb6f61d519e4ae |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9bb1a46081908547a2f27cbf3446 |
completed | March 8, 2026, 3:54 p.m. |
| PD | Predicate disambiguation | batch_69ad962195388190856013a2519c2b0f |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3:01 p.m.