Triple
T19411653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tripathi |
E485600
|
entity |
| Predicate | isHereditarySurname |
P135774
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Tripathi, isHereditarySurname, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isHereditarySurname Context triple: [Tripathi, isHereditarySurname, true]
-
A.
isSurname
Indicates that one entity is the family name (last name) of another entity.
-
B.
isDescriptiveSurname
Indicates that a surname is based on a descriptive characteristic or quality of the person or their ancestors.
-
C.
isCountableAsSurname
Indicates that something can be considered or treated as a valid surname for counting or classification purposes.
-
D.
isPatronymicSurname
Indicates that a surname is derived from the given name of a father or male ancestor, typically signifying "son/daughter of" that person.
-
E.
hasBaseSurname
Indicates that an entity’s surname is derived from, or fundamentally corresponds to, a specified base or canonical surname.
- F. None of above. chosen
Provenance (4 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_69d8e8d5162481909db12435d9535c1a |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e62af681288190ba2ec52d5adb6a22 |
completed | April 20, 2026, 1:32 p.m. |
| PD | Predicate disambiguation | batch_69e4fd68b1f881908d273de1fee81a75 |
completed | April 19, 2026, 4:06 p.m. |
| PDg | Predicate description generation | batch_69e5004c23308190a087b7941a90725f |
completed | April 19, 2026, 4:18 p.m. |
Created at: April 10, 2026, 1:37 p.m.