Triple
T25865205
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schwab's Pharmacy |
E651592
|
entity |
| Predicate | discoveryLegendInvolves |
P163855
|
FINISHED |
| Object | Hollywood talent scout |
—
|
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: Hollywood talent scout | Statement: [Schwab's Pharmacy, discoveryLegendInvolves, Hollywood talent scout]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: discoveryLegendInvolves Context triple: [Schwab's Pharmacy, discoveryLegendInvolves, Hollywood talent scout]
-
A.
knownForDiscovering
Indicates that one entity is recognized or notable for having discovered another entity.
-
B.
mentionsLegend
Indicates that one entity makes reference to or cites a legendary figure, story, or concept associated with another entity.
-
C.
bestKnownLegend
Indicates that one entity is the most prominent or widely recognized legendary story or myth associated with another entity.
-
D.
discoveredAs
Indicates that one entity was first identified, found, or recognized in the role or form specified by another entity.
-
E.
isDiscoveredBy
Indicates that something (such as an object, fact, or phenomenon) is found, identified, or revealed by a particular agent or entity.
- F. None of above. chosen
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_69e7ab3a199c81909227cb964cacfe24 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6416fbf4081909b0913c337927fc4 |
completed | May 2, 2026, 6:24 p.m. |
| PD | Predicate disambiguation | batch_69f63c6456608190b94e7c2e2c2a4824 |
completed | May 2, 2026, 6:03 p.m. |
| PDg | Predicate description generation | batch_69f63fd4f7448190930c723ba7cfce62 |
completed | May 2, 2026, 6:17 p.m. |
Created at: April 22, 2026, 8:07 a.m.