Triple
T31949315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indian Air Force A-50I Phalcon |
E815736
|
entity |
| Predicate | numberInService |
P203354
|
FINISHED |
| Object | 3 |
—
|
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: 3 | Statement: [Indian Air Force A-50I Phalcon, numberInService, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberInService Context triple: [Indian Air Force A-50I Phalcon, numberInService, 3]
-
A.
serviceNumber
Indicates a unique identifying number assigned to a service, used to reference, track, or distinguish that service from others.
-
B.
inService
Indicates that an entity is currently active, operational, or available for use in its intended role or function.
-
C.
serviceNumberOrUnit
Indicates that an entity is associated with a specific service number or organizational unit identifier.
-
D.
serviceNumbering
Indicates that a specific service is assigned or associated with a particular identifying number or code.
-
E.
serviceNumberApproximate
Indicates that one entity’s service number is approximately equal to, but not necessarily exactly the same as, another entity’s service number.
- 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_69f348f42d188190a33fc8d20ec50517 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a016777257081908841c5522dfa76e6 |
completed | May 11, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_6a0164e49bec8190af3c8626be9677a9 |
completed | May 11, 2026, 5:11 a.m. |
| PDg | Predicate description generation | batch_6a016775df2c81909448a0201f5f4af6 |
completed | May 11, 2026, 5:21 a.m. |
Created at: May 1, 2026, 12:07 a.m.