Triple
T29749742
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FAMAS family |
E752861
|
entity |
| Predicate | hasDesignLayout |
P177101
|
FINISHED |
| Object | bullpup |
—
|
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 | Statement: [FAMAS family, hasDesignLayout, bullpup]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDesignLayout Context triple: [FAMAS family, hasDesignLayout, bullpup]
-
A.
hasDesign
Indicates that one entity possesses, embodies, or is characterized by a particular design associated with another entity.
-
B.
hasDesignProperty
chosen
Indicates that an entity possesses a specific design-related characteristic, feature, or attribute.
-
C.
hasDesignContext
Indicates that something is associated with, or defined within, a particular design context or design environment.
-
D.
hasDesignSide
Indicates that one entity is located on, associated with, or corresponds to a particular side or face of another entity’s design.
-
E.
hasDesignOption
Indicates that an entity is associated with or offers a particular design alternative or configurable design choice.
- 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_69fd5f29b1988190877764ef2a399c7f |
completed | May 8, 2026, 3:57 a.m. |
| PD | Predicate disambiguation | batch_69fd5e30194c819085b5ce586122ab37 |
completed | May 8, 2026, 3:53 a.m. |
Created at: April 28, 2026, 7:53 p.m.