Triple
T31581057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RUT |
E805823
|
entity |
| Predicate | hasAssociatedProducts |
P3585
|
FINISHED |
| Object | exchange-traded funds |
—
|
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: exchange-traded funds | Statement: [RUT, hasAssociatedProducts, exchange-traded funds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAssociatedProducts Context triple: [RUT, hasAssociatedProducts, exchange-traded funds]
-
A.
hasProduct
chosen
Indicates that an entity possesses, offers, or is associated with a particular product.
-
B.
hasProductUser
Indicates that a product is associated with or used by a particular user.
-
C.
hasProductAttribute
Indicates that a product is associated with a specific attribute describing one of its characteristics or properties.
-
D.
relatedToProduct
Indicates a general association or connection between an entity and a specific product, without specifying the exact nature of that relationship.
-
E.
hasRelatedCategory
Indicates that one category is associated with another category through a non-hierarchical, contextually relevant relationship.
- 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_69f348d3a86c8190a3e5e539a4dd125f |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7886be6d8819095ec62e4f2cee858 |
completed | May 3, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69f7841440f48190b4346c08855951d2 |
completed | May 3, 2026, 5:21 p.m. |
Created at: April 30, 2026, 10:23 p.m.