Triple
T6539930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nasdaq Global Market |
E168258
|
entity |
| Predicate | includesInstruments |
P72278
|
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: [Nasdaq Global Market, includesInstruments, common stock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesInstruments Context triple: [Nasdaq Global Market, includesInstruments, common stock]
-
A.
usesInstrument
Indicates that an agent performs an action by employing a specific instrument or tool as the means to carry it out.
-
B.
alsoAppliesInstrument
Indicates that a condition, rule, or characteristic that applies to one instrument also applies to another instrument.
-
C.
usesInstrumentsOnStage
Indicates that an entity performs on stage while making use of musical instruments.
-
D.
instrumentalIn
Indicates that one entity serves as a crucial means, tool, or contributing factor in bringing about an outcome or enabling another entity’s action or effect.
-
E.
reliesOnInstrument
Indicates that an action or process depends on or is carried out using a particular instrument or tool.
- 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_69c68a51564081909e93aee0dbd9cca3 |
completed | March 27, 2026, 1:46 p.m. |
| NER | Named-entity recognition | batch_69c6ce07332481909a5a7964282eb776 |
completed | March 27, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69c6acf3e3708190b052ec774e607cb7 |
completed | March 27, 2026, 4:14 p.m. |
| PDg | Predicate description generation | batch_69c6ce0538f48190abf3160681901c17 |
completed | March 27, 2026, 6:35 p.m. |
Created at: March 27, 2026, 1:50 p.m.