Triple
T22508684
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prithi Chand |
E556457
|
entity |
| Predicate | sectNameDerivedFrom |
P77560
|
FINISHED |
| Object | his own name "Prithi" |
—
|
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: his own name "Prithi" | Statement: [Prithi Chand, sectNameDerivedFrom, his own name "Prithi"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sectNameDerivedFrom Context triple: [Prithi Chand, sectNameDerivedFrom, his own name "Prithi"]
-
A.
derivedFrom
Indicates that one entity originates, is obtained, or is developed from another source entity.
-
B.
isNamedSectionOf
Indicates that one entity is a specifically named section or subdivision that forms part of another entity.
-
C.
derivedBy
Indicates that one entity is obtained, produced, or inferred from another through some transformation, process, or reasoning.
-
D.
subbranchOf
Indicates that one entity is a subordinate or secondary branch derived from, and structurally dependent on, another entity.
-
E.
commonNameDerivedFrom
chosen
Indicates that the commonly used name of one entity originates from, or is derived based on, another entity.
- 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_69e11e555edc81909ca803587dafd747 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15d5ebe5881908a22d519128415f2 |
completed | April 29, 2026, 1:22 a.m. |
| PD | Predicate disambiguation | batch_69e898be31448190be5ae7f5656f0497 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:50 p.m.