Triple
T32123850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Big Baby |
E820446
|
entity |
| Predicate | sharedOwnerWith |
P3498
|
FINISHED |
| Object | Lots-o'-Huggin' Bear |
—
|
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: Lots-o'-Huggin' Bear | Statement: [Big Baby, sharedOwnerWith, Lots-o'-Huggin' Bear]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharedOwnerWith Context triple: [Big Baby, sharedOwnerWith, Lots-o'-Huggin' Bear]
-
A.
sharesOwnershipWith
chosen
Indicates that two or more entities jointly hold ownership rights or stakes in the same asset, resource, or organization.
-
B.
hasOwnerShare
Indicates that an entity holds a specified ownership stake or share in another entity or asset.
-
C.
sharesWith
Indicates that one entity gives another entity access to or use of something it possesses.
-
D.
sharesCustodyWith
Indicates that two or more parties jointly hold legal responsibility and decision-making authority for the care and upbringing of the same dependent, typically a child.
-
E.
privateOwnershipShare
Indicates the proportion or share of ownership in an entity that is held by private (non-governmental) owners.
- 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_69f34902d42c819083a8e6bba9a8bb9a |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ff45793d5c81909dc503ad1f714ee2 |
completed | May 9, 2026, 2:32 p.m. |
| PD | Predicate disambiguation | batch_69ff41cb0e088190a6e9b03cb20e5fad |
completed | May 9, 2026, 2:16 p.m. |
Created at: May 1, 2026, 12:29 a.m.