Triple
T7105295
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Achaeans |
E165565
|
entity |
| Predicate | sufferedLoss |
P24423
|
FINISHED |
| Object | many warriors killed at Troy |
—
|
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: many warriors killed at Troy | Statement: [Achaeans, sufferedLoss, many warriors killed at Troy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sufferedLoss Context triple: [Achaeans, sufferedLoss, many warriors killed at Troy]
-
A.
causedLossOf
Indicates that one entity brought about or was responsible for another entity experiencing a loss.
-
B.
significantLoss
chosen
Indicates that an entity has experienced a major or substantial decrease in value, quantity, or status beyond a normal or minor loss.
-
C.
sufferedDamageTo
Indicates that one entity has experienced harm, loss, or deterioration affecting another entity or one of its parts.
-
D.
lostDuring
Indicates that something ceased to be in possession or was no longer retained while a particular event, process, or time period was occurring.
-
E.
sufferedDestructionOf
Indicates that one entity experienced damage, ruin, or loss as a result of the destruction of another entity.
- 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_69c6887fcddc8190a5d58908f6dee590 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e5b892008190827fa1e5eab2e558 |
completed | March 27, 2026, 8:16 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c313e481908b61a23fc89f9332 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:42 p.m.