Triple
T28147574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rudy’s Rare Records |
E714524
|
entity |
| Predicate | shopNameInSeries |
P139054
|
FINISHED |
| Object | Rudy’s Rare Records |
—
|
NE NERFINISHED |
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: Rudy’s Rare Records | Statement: [Rudy’s Rare Records, shopNameInSeries, Rudy’s Rare Records]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shopNameInSeries Context triple: [Rudy’s Rare Records, shopNameInSeries, Rudy’s Rare Records]
-
A.
reportedlyStores
Indicates that an entity is said or believed, based on reports or claims, to store or hold another entity, without confirming that this storage actually occurs.
-
B.
hasShopName
chosen
Indicates that an entity (such as a shop or business) is associated with a specific shop name.
-
C.
hasRetailBoutiquesIn
Indicates that an entity operates or maintains retail boutiques located within a specified place or region.
-
D.
hasShoppingMallName
Indicates that an entity (such as a shopping mall) is associated with or identified by a specific name.
-
E.
showroomName
Indicates the name assigned to a particular showroom in the 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_69efd6b033208190bf74f80a147e2092 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f64173f85c8190a0e751a4029052d4 |
completed | May 2, 2026, 6:24 p.m. |
| PD | Predicate disambiguation | batch_69f63c6a8474819091b8c6fe98e3862d |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 9:57 p.m.