Triple
T13392588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Lemp sisters |
E319611
|
entity |
| Predicate | hasFictionalFamilyRelation |
P73825
|
FINISHED |
| Object | daughters of Adam Lemp |
—
|
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: daughters of Adam Lemp | Statement: [The Lemp sisters, hasFictionalFamilyRelation, daughters of Adam Lemp]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFictionalFamilyRelation Context triple: [The Lemp sisters, hasFictionalFamilyRelation, daughters of Adam Lemp]
-
A.
hasFictionalFamily
chosen
Indicates that an entity is associated with a family that exists only within a fictional or imaginary context.
-
B.
fictionalRelationship
Indicates a relationship that exists only within a fictional or imagined context between entities.
-
C.
hasFictionalFather
Indicates that one entity is the fictional father of another entity.
-
D.
hasFamilialTieTo
Indicates a relationship where two entities are connected by family bonds, such as by blood, marriage, or adoption.
-
E.
relationshipToCharacter
Indicates the specific type of personal, social, or narrative connection that one entity has to a given character.
- 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_69d806b886bc8190b676e7768b8e01c5 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dba0d74e5881909828854bba7d9a87 |
completed | April 12, 2026, 1:40 p.m. |
| PD | Predicate disambiguation | batch_69d9a03189908190a784a2755f8d81e1 |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:34 p.m.