Triple
T18538228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sherlock Gnomes |
E453020
|
entity |
| Predicate | usesCharacterType |
P49696
|
FINISHED |
| Object | garden gnomes |
—
|
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: garden gnomes | Statement: [Sherlock Gnomes, usesCharacterType, garden gnomes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesCharacterType Context triple: [Sherlock Gnomes, usesCharacterType, garden gnomes]
-
A.
usesCharacter
Indicates that one entity employs, incorporates, or relies on a particular character (such as a symbol, letter, or persona) in its form, function, or representation.
-
B.
usesCharactersAs
Indicates that one entity employs or incorporates specific characters (such as letters, symbols, or glyphs) from another entity for its representation or functioning.
-
C.
helpsCharacterType
Indicates that one character type provides assistance or support to another character type.
-
D.
hasTypicalCharacterType
Indicates that an entity is commonly associated with or exemplified by a particular type of character or persona.
-
E.
workCharacterType
chosen
Indicates that a work involves or features a character of a specified type or role.
- 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_69d8d387b5548190aa030dad2cb4947e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e534030bd88190b25b95305a12a0c1 |
completed | April 19, 2026, 7:58 p.m. |
| PD | Predicate disambiguation | batch_69e469e0025c81908f16ed4f922674af |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:37 a.m.