Triple
T25490957
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nandamuri family |
E638834
|
entity |
| Predicate | notableGenerationCount |
P92144
|
FINISHED |
| Object | three generations |
—
|
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: three generations | Statement: [Nandamuri family, notableGenerationCount, three generations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableGenerationCount Context triple: [Nandamuri family, notableGenerationCount, three generations]
-
A.
notableGeneration
Indicates that an entity is particularly distinguished or recognized among a specific generation or cohort.
-
B.
notableCount
chosen
Indicates the number of notable or distinguished items, entities, or instances associated with a given subject.
-
C.
notableDynastyGeneration
Indicates that one dynasty generation is notably significant or distinguished in relation to another within a historical or genealogical context.
-
D.
notableNumber
Indicates that a number associated with an entity is distinguished or significant in some notable way (e.g., record-setting, symbolic, or otherwise remarkable).
-
E.
denotesGeneration
Indicates that one entity originates, produces, or gives rise to another entity, establishing a generative or causal source-result relationship between them.
- 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_69e75dbbd2a88190b70e1e645de14b9a |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69fd05ba6b2c81909c62b46237d10365 |
completed | May 7, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69fd03039e48819082b6e12c5453885a |
completed | May 7, 2026, 9:24 p.m. |
Created at: April 21, 2026, 2:38 p.m.