Triple
T18662888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | the Swede |
E456245
|
entity |
| Predicate | boastsAbout |
P72385
|
FINISHED |
| Object | his fight at the hotel while in the saloon |
—
|
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: his fight at the hotel while in the saloon | Statement: [the Swede, boastsAbout, his fight at the hotel while in the saloon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: boastsAbout Context triple: [the Swede, boastsAbout, his fight at the hotel while in the saloon]
-
A.
boastedAgainst
Indicates that one entity spoke with excessive pride or self-satisfaction specifically directed at or in opposition to another entity.
-
B.
saidAbout
chosen
Indicates that a statement or assertion has been made concerning or in reference to a particular entity or subject.
-
C.
boonDetails
Indicates the specific terms, conditions, or characteristics associated with a granted benefit or favor within the relationship or action.
-
D.
promotes
Indicates that one entity actively supports, advances, or encourages the growth, adoption, or success of another entity or outcome.
-
E.
glorifies
Indicates that one entity praises, exalts, or represents another in an admiring or honor-enhancing way.
- 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_69d8d38f72b4819090a935175d9ca8af |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5508c0d088190bef46fb3a3001f10 |
completed | April 19, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69e478db7a248190a8c6584673773923 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:48 a.m.