Triple
T20650838
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norbert(a) the Norwegian Ridgeback |
E507486
|
entity |
| Predicate | keptIllegally |
P140919
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Norbert(a) the Norwegian Ridgeback, keptIllegally, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keptIllegally Context triple: [Norbert(a) the Norwegian Ridgeback, keptIllegally, true]
-
A.
keptIn
Indicates that one entity is stored, contained, or maintained inside another entity as its location or container.
-
B.
consideredIllegalUnder
Indicates that one entity is regarded as illegal or unlawful according to the laws, rules, or regulations defined by another entity.
-
C.
usedToDetain
Indicates that something serves or functioned as a means, tool, or facility for holding or confining someone against their will.
-
D.
circulatedIllegallyIn
Indicates that something was distributed or shared within a particular place or context in violation of laws or regulations.
-
E.
keptWith
Indicates that one entity is stored, maintained, or held together in association with another 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_69e0b4bf58c081908e52a4500e03ff83 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6af21e87c8190835bf2b2ef195626 |
completed | April 20, 2026, 10:56 p.m. |
| PD | Predicate disambiguation | batch_69e5c0315f5081908098707c6455e56e |
completed | April 20, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69e5c3caef50819093c8159fe8d6435b |
completed | April 20, 2026, 6:12 a.m. |
Created at: April 16, 2026, 11:43 a.m.