Triple
T12914372
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mil Mi-6 |
E308937
|
entity |
| Predicate | payloadExternal_kg |
P106985
|
FINISHED |
| Object | 9000 |
—
|
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: 9000 | Statement: [Mil Mi-6, payloadExternal_kg, 9000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: payloadExternal_kg Context triple: [Mil Mi-6, payloadExternal_kg, 9000]
-
A.
payloadSpecialist
Indicates that an entity serves in the role of a payload specialist, responsible for managing or operating specific payloads or experiments in a mission or operation.
-
B.
payloadCustomer
Indicates that a customer is associated with or carried as the payload within a given data structure, message, or transaction.
-
C.
usesPayload
Indicates that one entity employs or utilizes another entity as its payload in performing an action or function.
-
D.
payloadRole
Indicates the functional role or purpose that a payload has within a system, process, or interaction.
-
E.
secondaryPayload
Indicates that an entity serves as an additional or subordinate payload associated with a primary payload in an action or relationship.
- 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_69d7bdf92b588190acdf2a2291ac4590 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d971a0d6508190bca9668e9e06abfe |
completed | April 10, 2026, 9:54 p.m. |
| PD | Predicate disambiguation | batch_69d96fa9b7708190a9e9fa30f59ff580 |
completed | April 10, 2026, 9:46 p.m. |
| PDg | Predicate description generation | batch_69d9708a86bc8190bcdcf97e845bb413 |
completed | April 10, 2026, 9:50 p.m. |
Created at: April 9, 2026, 5:41 p.m.