Triple
T28301449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nalapani Fort |
E713719
|
entity |
| Predicate | centuryOfMajorConflict |
P145959
|
FINISHED |
| Object | 19th 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: 19th century | Statement: [Nalapani Fort, centuryOfMajorConflict, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centuryOfMajorConflict Context triple: [Nalapani Fort, centuryOfMajorConflict, 19th century]
-
A.
startOfMajorConflict
Indicates that one event marks the beginning or initial outbreak of a major conflict between parties.
-
B.
majorWar
Indicates a large-scale, intense armed conflict between major powers or involving substantial military forces and widespread impact.
-
C.
conflictEra
Indicates that two entities are associated with the same historical period or era of conflict.
-
D.
timePeriodOfMajorMilitaryActivity
chosen
Indicates the time span during which the primary or most significant military operations associated with an entity took place.
-
E.
majorConflictYear
Indicates the year in which a major conflict, such as a war or large-scale violent confrontation, took place or reached a defining point.
- 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_69efb524ab688190a1ce7ee7c9520932 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f64e37f7fc819083809149b6661e3c |
completed | May 2, 2026, 7:19 p.m. |
| PD | Predicate disambiguation | batch_69f64caede108190a35cc7cbfead866f |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 27, 2026, 11:35 p.m.