Triple
T37142342
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Falas |
E920147
|
entity |
| Predicate | resultOfSack |
P374
|
FINISHED |
| Object | destruction of Brithombar |
—
|
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: destruction of Brithombar | Statement: [Falas, resultOfSack, destruction of Brithombar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resultOfSack Context triple: [Falas, resultOfSack, destruction of Brithombar]
-
A.
sacks
Indicates that one entity tackles and brings another entity to the ground, typically behind a line of scrimmage or in a way that stops their progress.
-
B.
sackDate
Indicates the date on which a person was dismissed or removed from a position, role, or employment.
-
C.
result
chosen
Indicates that one entity is produced, caused, or brought about as an outcome or consequence of another entity or process.
-
D.
resultOfPursuit
Indicates that one event, state, or outcome occurs as a direct consequence of a preceding act of pursuit.
-
E.
outcomeOf
Indicates that one entity is the result, consequence, or product that arises from another entity, event, or process.
- 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_69f76e9e9d008190a250b0387c992c74 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fdbaa226708190b8ed96e93aad38de |
completed | May 8, 2026, 10:27 a.m. |
| PD | Predicate disambiguation | batch_69fdb58b07e48190837e00966de050d4 |
completed | May 8, 2026, 10:06 a.m. |
Created at: May 3, 2026, 4:15 p.m.