Triple
T22690081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dow Jones U.S. Health Care Index |
E561027
|
entity |
| Predicate | componentListingLocation |
P71609
|
FINISHED |
| Object | U.S.-listed companies |
—
|
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: U.S.-listed companies | Statement: [Dow Jones U.S. Health Care Index, componentListingLocation, U.S.-listed companies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: componentListingLocation Context triple: [Dow Jones U.S. Health Care Index, componentListingLocation, U.S.-listed companies]
-
A.
componentListingRequirement
Indicates that one entity is required to list, specify, or disclose the components or constituent parts of another entity.
-
B.
componentPosition
Indicates the spatial or logical placement of a component relative to a larger structure or system.
-
C.
exchangeListingOfComponents
chosen
Indicates that components are listed or registered for trading or exchange between parties or systems.
-
D.
locationInCableAssembly
Indicates a relationship where an element is positioned or situated within a specific cable assembly.
-
E.
plateLocation
Indicates the spatial position or placement of a plate relative to a reference location or object.
- 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_69e2454d71b48190a1f80af9f82b6fcf |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1789a1fd08190bce5fa0babe695d3 |
completed | April 29, 2026, 3:18 a.m. |
| PD | Predicate disambiguation | batch_69ee62b2259c819091ed1387a748b9f3 |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:13 p.m.