Triple
T23024447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Puran |
E573261
|
entity |
| Predicate | isNotableNameOf |
P150719
|
FINISHED |
| Object | multiple individuals in India |
—
|
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: multiple individuals in India | Statement: [Puran, isNotableNameOf, multiple individuals in India]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNotableNameOf Context triple: [Puran, isNotableNameOf, multiple individuals in India]
-
A.
isNotable
Indicates that an entity is recognized as significant, prominent, or worthy of attention within a particular context or domain.
-
B.
hasNotableNamesakeType
Indicates that an entity has a notable namesake of a specified type (such as a person, place, or work) that shares its name.
-
C.
notableLocalName
Indicates that an entity is known by a notable or commonly used local name within a specific region or community.
-
D.
namedIn
Indicates that one entity is explicitly mentioned or referenced by name within another entity (such as a document, statement, or record).
-
E.
hasNotablePropertyNamedAfter
Indicates that an entity possesses a notable property or attribute that is named in honor of, or derived from, another entity.
- 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_69e245b821008190b0e09cb02092aae1 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1847b86688190b678d0d09ecd3c3d |
completed | April 29, 2026, 4:09 a.m. |
| PD | Predicate disambiguation | batch_69ef3ba004a48190885aece88efd1f52 |
completed | April 27, 2026, 10:34 a.m. |
| PDg | Predicate description generation | batch_69ef538b29c081908fa56ee35a1dcee7 |
completed | April 27, 2026, 12:16 p.m. |
Created at: April 17, 2026, 3:52 p.m.