Triple
T34238214
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pebbles |
E878389
|
entity |
| Predicate | isAssociatedWithFranchise |
P9673
|
FINISHED |
| Object | The Flintstones franchise |
—
|
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: The Flintstones franchise | Statement: [Pebbles, isAssociatedWithFranchise, The Flintstones franchise]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAssociatedWithFranchise Context triple: [Pebbles, isAssociatedWithFranchise, The Flintstones franchise]
-
A.
associatedFranchise
chosen
Indicates a relationship where one entity is linked to, or belongs within, a particular franchise or franchise universe.
-
B.
formedByFranchise
Indicates that something (such as a team, organization, or unit) was created or established as a result of a franchise agreement or franchising process.
-
C.
hasParentFranchise
Indicates that one franchise entity is the parent or overarching franchise of another franchise entity.
-
D.
franchiseOf
Indicates that one entity operates as a franchise belonging to or licensed by another entity.
-
E.
usedByFranchise
Indicates that something (such as a resource, asset, or element) is utilized or employed by a particular franchise.
- 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_69f349b22d8c819096b22df268382aa9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71362f1448190985a80ce7af475cb |
completed | May 3, 2026, 9:20 a.m. |
| PD | Predicate disambiguation | batch_69f7127884388190884f23d181a65d19 |
completed | May 3, 2026, 9:16 a.m. |
Created at: May 1, 2026, 1:56 a.m.