Triple
T18782177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hyderabad Police Action |
E459283
|
entity |
| Predicate | surrenderDateOfHyderabadForces |
P4667
|
FINISHED |
| Object | 1948-09-17 |
—
|
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: 1948-09-17 | Statement: [Hyderabad Police Action, surrenderDateOfHyderabadForces, 1948-09-17]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: surrenderDateOfHyderabadForces Context triple: [Hyderabad Police Action, surrenderDateOfHyderabadForces, 1948-09-17]
-
A.
garrisonSurrenderedTo
Indicates that a defending military garrison formally capitulated and yielded control to another party.
-
B.
dateOfSurrenderOfImamShamil
Indicates the specific date on which Imam Shamil formally surrendered.
-
C.
surrenderDate
chosen
Indicates the date on which an entity formally yields control, possession, or rights, typically ending its claim or resistance.
-
D.
timeOfSurrender
Indicates the specific point in time at which an entity formally surrenders or yields.
-
E.
surrenderedIn
Indicates that an entity yielded or gave up control, power, or resistance within a specific event, context, or situation.
- 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_69d8d396f54c8190ba49db31e8743842 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5977d7c5c8190ab2aadb47283965d |
completed | April 20, 2026, 3:03 a.m. |
| PD | Predicate disambiguation | batch_69e48d16dd34819096e096d0c0e4c15c |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:52 a.m.