Triple
T21555032
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FGR.2 |
E531867
|
entity |
| Predicate | hasDesignationMeaning |
P144222
|
FINISHED |
| Object | Fighter Ground-attack Reconnaissance |
—
|
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: Fighter Ground-attack Reconnaissance | Statement: [FGR.2, hasDesignationMeaning, Fighter Ground-attack Reconnaissance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDesignationMeaning Context triple: [FGR.2, hasDesignationMeaning, Fighter Ground-attack Reconnaissance]
-
A.
hasDesignation
Indicates that an entity holds or is assigned a specific title, label, or formal designation.
-
B.
hasDesignationBy
Indicates that one entity has been formally assigned or labeled with a specific designation by another entity.
-
C.
hasDesignationForm
Indicates that an entity is associated with a particular form or format used for its designation or naming.
-
D.
hasDesignationNumber
Indicates that an entity is associated with a specific official designation or identification number.
-
E.
familyDesignationMeaning
Indicates the specific role, status, or significance that a given family-related designation conveys within a familial or kinship context.
- 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_69e0c460232c81908de2c3819d17c00e |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eed2de1c248190b303a4a55b022374 |
completed | April 27, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69e6320766308190ba5dca2f7c826aa4 |
completed | April 20, 2026, 2:02 p.m. |
| PDg | Predicate description generation | batch_69e633bf34c481909925d8dc1a633a65 |
completed | April 20, 2026, 2:10 p.m. |
Created at: April 16, 2026, 6:29 p.m.