Triple
T10004091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AN/APG-63 |
E198198
|
entity |
| Predicate | introducedForPlatform |
P3018
|
FINISHED |
| Object | early F-15A/B models |
—
|
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: early F-15A/B models | Statement: [AN/APG-63, introducedForPlatform, early F-15A/B models]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedForPlatform Context triple: [AN/APG-63, introducedForPlatform, early F-15A/B models]
-
A.
introducedFor
chosen
Indicates that one entity was presented or brought to the attention of another entity for a specific purpose or role.
-
B.
introducedInSystem
Indicates that an entity was first added, implemented, or made available within a particular system.
-
C.
introducedFrom
Indicates that one entity was brought, originated, or caused to appear in a context, system, or environment by another entity.
-
D.
announcedPlatform
Indicates that an entity has publicly revealed or introduced a particular platform (such as a system, service, or technology).
-
E.
supportedPlatform
Indicates that one entity (such as a system, application, or service) is compatible with and can operate on a particular platform.
- 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_69ca830fcca48190bbbd9b20c233835f |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cdcd141ec08190b857fe7e15a8df93 |
completed | April 2, 2026, 1:57 a.m. |
| PD | Predicate disambiguation | batch_69cd1da2cf9081908a6c0eb5247d0bc2 |
completed | April 1, 2026, 1:29 p.m. |
Created at: March 30, 2026, 8:51 p.m.