Triple
T25939941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Krinklesac |
E653666
|
entity |
| Predicate | familyNameOfFictionalFamily |
P148237
|
FINISHED |
| Object | Krinklesac family |
—
|
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: Krinklesac family | Statement: [Krinklesac, familyNameOfFictionalFamily, Krinklesac family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: familyNameOfFictionalFamily Context triple: [Krinklesac, familyNameOfFictionalFamily, Krinklesac family]
-
A.
familySurnameInStory
Indicates that a particular family surname appears within the narrative or context of a given story.
-
B.
familyNameIn
Indicates that an entity has a specified family name (surname) in a particular language or cultural context.
-
C.
familyNameOfMembers
chosen
Indicates that the specified family name is shared by the members of a given group or family.
-
D.
hasFictionalFamily
Indicates that an entity is associated with a family that exists only within a fictional or imaginary context.
-
E.
familyName
Indicates that one entity is the family (last) name associated with another entity (typically a person).
- 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_69e7ab3fd2f881908837305e4ba98011 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6456608190b94e7c2e2c2a4824 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 22, 2026, 8:40 a.m.