Triple
T10252867
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ragtime |
E240386
|
entity |
| Predicate | featuresFictionalFamily |
P40767
|
FINISHED |
| Object | Mother’s family |
—
|
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: Mother’s family | Statement: [Ragtime, featuresFictionalFamily, Mother’s family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresFictionalFamily Context triple: [Ragtime, featuresFictionalFamily, Mother’s family]
-
A.
hasFictionalFamily
Indicates that an entity is associated with a family that exists only within a fictional or imaginary context.
-
B.
featuresFamily
chosen
Indicates that something includes, presents, or highlights a family as a central element or subject.
-
C.
featuresCharactersFrom
Indicates that one entity (such as a work or production) includes or presents characters originating from another entity.
-
D.
familyCharacteristic
Indicates that a particular trait, feature, or quality is shared within or typical of members of the same family.
-
E.
featuresFictionalProgram
Indicates that a work includes or presents a fictional program (such as a TV show, software, or in-universe broadcast) as part of its content.
- 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_69d381a7e198819090280d5ab885d59e |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d328272c8190a3548d7f7f38cfc4 |
completed | April 7, 2026, 9:49 a.m. |
| PD | Predicate disambiguation | batch_69d4d1ebd6c88190a1f3f4a72a99d6fe |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:29 a.m.