Triple
T37858375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Forces of Hemu |
E944254
|
entity |
| Predicate | timeOfMajorDefeat |
P182410
|
FINISHED |
| Object | 1556 |
—
|
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: 1556 | Statement: [Forces of Hemu, timeOfMajorDefeat, 1556]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeOfMajorDefeat Context triple: [Forces of Hemu, timeOfMajorDefeat, 1556]
-
A.
dateOfMajorDefeat
Indicates the specific date on which an entity experienced a significant or decisive defeat.
-
B.
dateOfMilitaryDefeat
chosen
Indicates the specific date on which a military force or entity was defeated in a conflict or battle.
-
C.
locationOfMajorDefeat
Indicates the place where a significant or decisive defeat of a party occurred.
-
D.
significantDefeat
Indicates that one entity has decisively and substantially defeated another, implying a clear and impactful victory rather than a narrow or marginal one.
-
E.
timeOfMajorBattle
Indicates the specific time at which a major battle took place.
- 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_69f76eee2f9c8190b1272aa2ee55ebf5 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fe5ec9028081909ae3d6fbe2f4cbbc |
completed | May 8, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69fe5e1d715881909fc516fafc707644 |
completed | May 8, 2026, 10:05 p.m. |
Created at: May 3, 2026, 4:19 p.m.