Triple
T10468589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naveen |
E246866
|
entity |
| Predicate | hasTypicalNameCategory |
P75425
|
FINISHED |
| Object | modern Indian name |
—
|
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: modern Indian name | Statement: [Naveen, hasTypicalNameCategory, modern Indian name]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalNameCategory Context triple: [Naveen, hasTypicalNameCategory, modern Indian name]
-
A.
hasNameLengthCategory
Indicates that an entity is associated with a classification describing the length of its name (e.g., short, medium, long).
-
B.
hasNameCharacteristic
chosen
Indicates that an entity possesses a specific quality or attribute related to its name.
-
C.
hasTypicalCharacterType
Indicates that an entity is commonly associated with or exemplified by a particular type of character or persona.
-
D.
typicalNameLength
Indicates the usual or characteristic number of characters in the names of entities in a given context.
-
E.
hasNormativeCategory
Indicates that something is associated with a particular normative category, such as a standard, rule, or evaluative classification that prescribes how it ought to be regarded or treated.
- 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_69d381c16c248190a2fe5b471e584e9c |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d5092ef810819093a4d1df83aeac09 |
completed | April 7, 2026, 1:39 p.m. |
| PD | Predicate disambiguation | batch_69d4fb84bafc8190819757b93620508a |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:20 p.m.