Triple
T8721828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FAMAS F1 |
E207028
|
entity |
| Predicate | ambidextrousUse |
P84267
|
FINISHED |
| Object | requires bolt and case deflector change |
—
|
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: requires bolt and case deflector change | Statement: [FAMAS F1, ambidextrousUse, requires bolt and case deflector change]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ambidextrousUse Context triple: [FAMAS F1, ambidextrousUse, requires bolt and case deflector change]
-
A.
handedness
Indicates the preference or dominance of one hand over the other in performing actions or tasks.
-
B.
hasArms
Indicates that an entity possesses arms as physical appendages.
-
C.
isToolOf
Indicates that one entity functions as an instrument or means used by another entity to perform tasks or achieve goals.
-
D.
rightHandedComponent
Indicates that one entity functions as the right-handed component or counterpart within a paired or bilateral relationship to another entity.
-
E.
armType
Indicates the specific kind or configuration of an arm associated with an 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_69ca835811d8819081ea00fd2a2c9a1c |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5d03f0848190a50c77e5cd028ee7 |
completed | March 31, 2026, 11:47 p.m. |
| PD | Predicate disambiguation | batch_69cc457093188190959287a6458651c6 |
completed | March 31, 2026, 10:06 p.m. |
| PDg | Predicate description generation | batch_69cc489dd528819084ed5d88bd8bb3d6 |
completed | March 31, 2026, 10:20 p.m. |
Created at: March 30, 2026, 6:36 p.m.