Triple
T8721881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FAMAS Félin |
E207029
|
entity |
| Predicate | opticsType |
P7239
|
FINISHED |
| Object | integrated telescopic sight |
—
|
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: integrated telescopic sight | Statement: [FAMAS Félin, opticsType, integrated telescopic sight]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opticsType Context triple: [FAMAS Félin, opticsType, integrated telescopic sight]
-
A.
usesOpticsType
chosen
Indicates that one entity employs or is characterized by a specific type of optical system or technology.
-
B.
lensType
Indicates the specific kind or category of lens associated with or used by an entity.
-
C.
opticalDesign
Indicates a relationship where one entity is responsible for creating, specifying, or defining the optical configuration or characteristics of another entity.
-
D.
opticalProperty
Indicates a relationship where an entity has or is characterized by a specific optical property, such as how it interacts with or responds to light.
-
E.
sightType
Indicates the specific kind or category of sight or visual perception associated with an entity or event.
- 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_69ca835811d8819081ea00fd2a2c9a1c |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5d0609f48190adc56226724b16c6 |
completed | March 31, 2026, 11:47 p.m. |
| PD | Predicate disambiguation | batch_69cc457093188190959287a6458651c6 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:36 p.m.