Triple
T13234056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Moghul |
E315096
|
entity |
| Predicate | featuresHistoricalFigures |
P34335
|
FINISHED |
| Object | Mughal rulers |
—
|
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: Mughal rulers | Statement: [The Moghul, featuresHistoricalFigures, Mughal rulers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresHistoricalFigures Context triple: [The Moghul, featuresHistoricalFigures, Mughal rulers]
-
A.
historicalFigure
Indicates that an entity is recognized as a notable person from the past who played a significant role in history.
-
B.
historicalPeople
chosen
Indicates that the related entities are people who lived in or are associated with a past historical period or context.
-
C.
addressesHistoricalFigure
Indicates that one entity directly speaks or writes to a person recognized as a historical figure.
-
D.
roleInHumanHistory
Indicates the function, influence, or significance that an entity has had within the course of human history.
-
E.
historicalFigureDocumented
Indicates that there exists a record or account documenting the historical figure in some form of historical source.
- 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_69d806affc688190a25b6ccc588e9c72 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98d36bdf8819099949b1e0e6902d3 |
completed | April 10, 2026, 11:52 p.m. |
| PD | Predicate disambiguation | batch_69d98bcb21648190aef241de1e7887e2 |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:22 p.m.