Triple
T25917251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schneider’s Bakery |
E653066
|
entity |
| Predicate | basedOnNetworkLot |
P167728
|
FINISHED |
| Object | Nickelodeon-related studio facilities |
—
|
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: Nickelodeon-related studio facilities | Statement: [Schneider’s Bakery, basedOnNetworkLot, Nickelodeon-related studio facilities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basedOnNetworkLot Context triple: [Schneider’s Bakery, basedOnNetworkLot, Nickelodeon-related studio facilities]
-
A.
basedOnNetwork
Indicates that something is determined, derived, or operates according to a particular network or network-related characteristics.
-
B.
basedOnIP
Indicates that the relationship or action is determined or derived from an entity’s IP address.
-
C.
basedOnBidFor
Indicates that one action, decision, or entity is determined or derived from a specific bid submitted in a bidding process.
-
D.
usedByNetwork
Indicates that something is utilized or operated by a particular network.
-
E.
basedOnChannel
Indicates that something is determined, derived, or decided according to a particular channel as its basis or reference.
- 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_69e7ab3e025c819086771607157f0015 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f66cf092c881908d7034c9c2bc61d5 |
completed | May 2, 2026, 9:30 p.m. |
| PD | Predicate disambiguation | batch_69f66abddc448190a488852f8abdeb2c |
completed | May 2, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69f66c59de9881909ebbb7b0ae7ab495 |
completed | May 2, 2026, 9:27 p.m. |
Created at: April 22, 2026, 8:31 a.m.