Triple
T32719667
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Potato Head Kids |
E836634
|
entity |
| Predicate | hasIPType |
P174838
|
FINISHED |
| Object | licensed character brand |
—
|
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: licensed character brand | Statement: [Potato Head Kids, hasIPType, licensed character brand]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIPType Context triple: [Potato Head Kids, hasIPType, licensed character brand]
-
A.
hasIP
Indicates that one entity possesses, is assigned, or is associated with a specific IP address.
-
B.
usesIP
Indicates that one entity makes use of, operates through, or is associated with a particular IP address.
-
C.
hasISP
Indicates that an entity is subscribed to or uses a particular Internet Service Provider.
-
D.
usesIPProtocol
Indicates that one entity communicates or operates using a specific IP (Internet Protocol) version or protocol.
-
E.
hasInfrastructureType
Indicates that an entity possesses or is associated with a specific category or type of infrastructure.
- 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_69f34935455881909088975d79460418 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6c889dd208190a7b71d36c2a88624 |
completed | May 3, 2026, 4:01 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f617c08190a70ba880210f908c |
completed | May 3, 2026, 3:41 a.m. |
| PDg | Predicate description generation | batch_69f6c77500a08190b2bdeca33bd2ac08 |
completed | May 3, 2026, 3:56 a.m. |
Created at: May 1, 2026, 1:11 a.m.