Triple
T36938356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bash |
E913676
|
entity |
| Predicate | secondaryAbility |
P200253
|
FINISHED |
| Object | rolling charge |
—
|
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: rolling charge | Statement: [Bash, secondaryAbility, rolling charge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondaryAbility Context triple: [Bash, secondaryAbility, rolling charge]
-
A.
secondaryFunction
Indicates that an entity has an additional, supporting role or purpose beyond its primary function.
-
B.
secondarySense
Indicates that one sense or meaning of an expression is a secondary or less primary interpretation relative to another sense.
-
C.
secondaryAction
Indicates that an entity performs or is associated with an additional, supporting, or less primary action relative to a main action.
-
D.
secondaryActivity
Indicates that an entity engages in an additional, non-primary activity or role alongside its main activity.
-
E.
sonAbility
Indicates that a son possesses or demonstrates a particular ability or capability in relation to another entity.
- F. None of above. chosen
Provenance (4 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_69f76e8a6a5c81909c1febf32bf3fe23 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ff7c96e6dc8190b89554480ebcea39 |
completed | May 9, 2026, 6:27 p.m. |
| PD | Predicate disambiguation | batch_69ff7c2381748190ad9a2176e0e478cd |
completed | May 9, 2026, 6:25 p.m. |
| PDg | Predicate description generation | batch_69ff7c96036c8190bfae5ec9b5a1965f |
completed | May 9, 2026, 6:27 p.m. |
Created at: May 3, 2026, 4:13 p.m.