Triple
T26160584
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Madhavdev College |
E660096
|
entity |
| Predicate | hasNamesakeCentury |
P89519
|
FINISHED |
| Object | 16th century |
—
|
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: 16th century | Statement: [Madhavdev College, hasNamesakeCentury, 16th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNamesakeCentury Context triple: [Madhavdev College, hasNamesakeCentury, 16th century]
-
A.
hasEponymCentury
Indicates that something is named after a person associated with a particular century.
-
B.
associatedWithCenturyOfNameBearer
chosen
Indicates that an entity is linked to the historical century in which the person (name bearer) associated with it lived or is primarily known.
-
C.
existedInCentury
Indicates that an entity existed or was present during a specified century.
-
D.
namedAfterCentury
Indicates that something is named after a specific century, typically reflecting that century’s time period or characteristics.
-
E.
hasCenturyOfPersonCommemorated
Indicates the century in which the person being commemorated lived or was active.
- 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_69ee5bc5a9908190899d39ce95c6d215 |
completed | April 26, 2026, 6:39 p.m. |
| NER | Named-entity recognition | batch_69f6b49436b0819094e21603054d05d4 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a5fd8481909433e923c5e24e55 |
completed | May 3, 2026, 2:32 a.m. |
Created at: April 26, 2026, 8:30 p.m.