Triple
T29749730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Le Clairon |
E752860
|
entity |
| Predicate | referredFirearmConfiguration |
P101195
|
FINISHED |
| Object | bullpup layout |
—
|
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: bullpup layout | Statement: [Le Clairon, referredFirearmConfiguration, bullpup layout]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: referredFirearmConfiguration Context triple: [Le Clairon, referredFirearmConfiguration, bullpup layout]
-
A.
designedForFirearm
Indicates that something is specifically created or intended to be used with a firearm.
-
B.
armamentConfiguration
chosen
Indicates how weapons or armaments are arranged, equipped, or configured on an entity in a given context.
-
C.
firearmActionType
Indicates the specific type or category of action performed with or by a firearm (such as firing, loading, carrying, or modifying).
-
D.
prohibitedWeapon
Indicates that an entity is classified as a weapon whose possession, use, or transfer is forbidden by law, regulation, or policy.
-
E.
prohibitedWeaponType
Indicates that a particular type of weapon is classified as not allowed or forbidden under specified rules, laws, or agreements.
- 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_69f0d62c84cc8190846f80ae04fdf8ec |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fbbc49da8c8190902bbb05d2477cab |
completed | May 6, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69fbb13f34b08190bbbb220ac1e6e666 |
completed | May 6, 2026, 9:23 p.m. |
Created at: April 28, 2026, 7:53 p.m.