Triple
T20112270
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Summer Lane |
E490362
|
entity |
| Predicate | ageRelativeDescription |
P125146
|
FINISHED |
| Object | younger sister of Jane Lane |
—
|
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: younger sister of Jane Lane | Statement: [Summer Lane, ageRelativeDescription, younger sister of Jane Lane]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ageRelativeDescription Context triple: [Summer Lane, ageRelativeDescription, younger sister of Jane Lane]
-
A.
relativeAgeStatus
chosen
Indicates a comparative relationship specifying how the age of one entity relates to the age of another (e.g., older, younger, or same age).
-
B.
relativeByBirth
Indicates that two entities are related to each other through a biological family connection established by birth.
-
C.
hasRelativeAge
Indicates that one entity has an age that is defined or compared in relation to the age of another entity.
-
D.
relationshipToYoungerFamily
Indicates a familial relationship where one person is related to another who is younger in age within the family.
-
E.
timeRelativeToBirth
Indicates the temporal position of an event or state relative to an entity’s birth (e.g., before, at, or after birth).
- 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_69da62636cc08190982cc71733a17b8d |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e666e162108190b19c9559218c8fd6 |
completed | April 20, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69e54cf788188190a46cc49c9ce7617f |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 11:29 p.m.