Triple
T1411607
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dow Jones U.S. Auto Manufacturers Index |
E31816
|
entity |
| Predicate | componentListing |
P19878
|
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. Auto Manufacturers Index, componentListing, U.S.-listed companies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: componentListing Context triple: [Dow Jones U.S. Auto Manufacturers Index, componentListing, U.S.-listed companies]
-
A.
componentsDefinition
Indicates that one entity defines or specifies the components that make up another entity.
-
B.
component1
Indicates that one entity functions as a constituent or part of another entity within a larger whole.
-
C.
componentType
Indicates that one entity specifies or classifies the kind or category of component that another entity represents or uses.
-
D.
componentOrder
Indicates the relative sequence or arrangement of components within a larger structure or system.
-
E.
componentUniverse
chosen
Indicates that one entity is the complete set or universe of components from which the other entity’s parts or elements are drawn.
- 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_69a49919a994819086528951bc224775 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c3e1da988190bc7c187e193539b6 |
completed | March 1, 2026, 10:55 p.m. |
| PD | Predicate disambiguation | batch_69a4bf048b648190ab77d9b45cb4855f |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:59 p.m.