Triple
T35748089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Divas’ Dream |
E1033240
|
entity |
| Predicate | hasCollectionSegment |
P43255
|
FINISHED |
| Object | Divas’ Dream jewelry |
E1033240
|
NE 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: Divas’ Dream jewelry | Statement: [Divas’ Dream, hasCollectionSegment, Divas’ Dream jewelry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCollectionSegment Context triple: [Divas’ Dream, hasCollectionSegment, Divas’ Dream jewelry]
-
A.
hasSegmentWith
Indicates that an entity contains or includes at least one segment that satisfies a specified condition or matches a given segment.
-
B.
hasCollectionSection
chosen
Indicates that an entity includes or is organized into a specific section within a larger collection.
-
C.
hasCollection
Indicates that an entity possesses, maintains, or is associated with a set or group of related items treated as a collection.
-
D.
hasCollectionAt
Indicates that a collection or gathering of items, data, or resources is located, stored, or maintained at a specific place or context.
-
E.
hasSegmentFrom
Indicates that something includes or contains a segment that originates from or is derived from another specified source.
- F. None of above.
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_69f76e119d508190a3873cb302063832 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037ce70f54819082946dad8d380825 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a387d2b2a688190861708c061f795dc |
completed | June 22, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_6a037a069e6c8190857b611fffb7b867 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:06 p.m.