Triple
T1409876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | D. Udaya Kumar |
E31778
|
entity |
| Predicate | designIncorporates |
P1529
|
FINISHED |
| Object | Devanagari letter Ra |
—
|
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: Devanagari letter Ra | Statement: [D. Udaya Kumar, designIncorporates, Devanagari letter Ra]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designIncorporates Context triple: [D. Udaya Kumar, designIncorporates, Devanagari letter Ra]
-
A.
designUse
Indicates that one entity is used as a design basis, purpose, or intended functional use for another entity.
-
B.
designedWith
Indicates that one entity was created, planned, or developed using another entity as a tool, method, or guiding basis in its design process.
-
C.
designedIn
Indicates that something was created, planned, or conceived during a particular time period or at a specific location.
-
D.
designBureau
Indicates that an entity functions as a design bureau responsible for planning, developing, or engineering designs for another entity or project.
-
E.
hasDesign
chosen
Indicates that one entity possesses, embodies, or is characterized by a particular design associated with 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_69a49918e1f88190ba610f9dc8114578 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c3e0bfd08190a50820bc7585c28f |
completed | March 1, 2026, 10:55 p.m. |
| PD | Predicate disambiguation | batch_69a4bf048b648190ab77d9b45cb4855f |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:59 p.m.