Triple
T26374443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | L-60 Brigadýr |
E660854
|
entity |
| Predicate | hasRoleVariant |
P114861
|
FINISHED |
| Object | agricultural version |
—
|
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: agricultural version | Statement: [L-60 Brigadýr, hasRoleVariant, agricultural version]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoleVariant Context triple: [L-60 Brigadýr, hasRoleVariant, agricultural version]
-
A.
hasVariantRole
chosen
Indicates that an entity participates in a context or process while assuming an alternative or modified role compared to its primary or canonical role.
-
B.
hasRole
Indicates that an entity occupies, performs, or is assigned a specific role or function in relation to another entity or context.
-
C.
hasVariant
Indicates that one entity exists as an alternative form, version, or variation of another entity.
-
D.
hasRankVariant
Indicates that one entity is an alternative or variant form of another entity’s rank or hierarchical level.
-
E.
hasRoleCharacteristic
Indicates that an entity possesses a specific characteristic, quality, or attribute associated with a particular role.
- 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_69ee812a698881908d6a58265995fa39 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b78f29481908cc8f390496dee97 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 26, 2026, 11 p.m.