Triple
T3038982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joint Advanced Strike Technology program |
E83078
|
entity |
| Predicate | typeOfTechnologyProgram |
P1482
|
FINISHED |
| Object | joint-service program |
—
|
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: joint-service program | Statement: [Joint Advanced Strike Technology program, typeOfTechnologyProgram, joint-service program]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfTechnologyProgram Context triple: [Joint Advanced Strike Technology program, typeOfTechnologyProgram, joint-service program]
-
A.
technologyType
chosen
Indicates the specific kind or category of technology associated with an entity or relationship.
-
B.
programType
Indicates the category or kind of program to which an entity belongs or with which it is associated.
-
C.
programmingLanguage
Indicates that one entity is a programming language used to create, control, or interact with the other entity.
-
D.
languageOfProgramming
Indicates that one entity is a programming language used to implement, develop, or script the other entity.
-
E.
languageOfPrimaryProgramming
Indicates the programming language that is primarily used to implement or develop a given entity.
- 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_69ad8b2298908190a7cb4e9bdbf064d0 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9b2fa52c8190a7860f762d5232ab |
completed | March 8, 2026, 3:52 p.m. |
| PD | Predicate disambiguation | batch_69ad961fc62c819087c4c3a44b00847d |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3:01 p.m.