Triple
T22280787
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sandbar Fight |
E550723
|
entity |
| Predicate | hasInvolvedActivity |
P74692
|
FINISHED |
| Object | pistol duel |
—
|
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: pistol duel | Statement: [Sandbar Fight, hasInvolvedActivity, pistol duel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInvolvedActivity Context triple: [Sandbar Fight, hasInvolvedActivity, pistol duel]
-
A.
hasBeenInvolvedIn
chosen
Indicates that an entity has participated in, taken part in, or been connected to a particular event, activity, or situation.
-
B.
hasActivityIn
Indicates that an entity engages in or performs a particular activity within a specified context, location, or domain.
-
C.
hasMemberInvolvedIn
Indicates that a group or collective entity has at least one of its members participating in or engaged with a specified activity, event, or situation.
-
D.
hasSubjectActivity
Indicates that an entity is associated with or participates in a particular activity as its subject.
-
E.
hasBasedActivity
Indicates that one activity is founded on, derived from, or primarily driven by another underlying activity.
- 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_69e11e44d538819097c6b8f333af3352 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f14eab4f848190b1a8ba70f9fb0581 |
completed | April 29, 2026, 12:19 a.m. |
| PD | Predicate disambiguation | batch_69e72ff0363081909f794d19c8a64837 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:40 p.m.