Triple
T26135539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neo-Vaishnavite movement in Assam |
E659370
|
entity |
| Predicate | flourishedCentury |
P6262
|
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: [Neo-Vaishnavite movement in Assam, flourishedCentury, 16th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flourishedCentury Context triple: [Neo-Vaishnavite movement in Assam, flourishedCentury, 16th century]
-
A.
flourishedInCentury
chosen
Indicates that an entity experienced its peak activity, influence, or development during a specified century.
-
B.
flourishedToCentury
Indicates the century during which an entity reached its peak activity, prominence, or flourishing.
-
C.
flourishedUntilCentury
Indicates the last century during which an entity (such as a person, culture, or institution) was active, prominent, or at its peak before declining or ceasing to flourish.
-
D.
flourishedDuring
Indicates that an entity was active, thriving, or at its peak during a specified time period or era.
-
E.
declaredInCentury
Indicates that something (such as an event, work, or concept) was formally declared or proclaimed during a specified century.
- 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_69ee5bc3c20c8190bf2cf272f4170e95 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f60b96c1ac8190adc0ceb44507777e |
completed | May 2, 2026, 2:35 p.m. |
| PD | Predicate disambiguation | batch_69f5b0021da88190bdd4cf2698c23edf |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 26, 2026, 8:17 p.m.