Triple
T15764915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | F-16 program |
E382194
|
entity |
| Predicate | includesBlockSeries |
P22382
|
FINISHED |
| Object | Block 10 |
—
|
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: Block 10 | Statement: [F-16 program, includesBlockSeries, Block 10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesBlockSeries Context triple: [F-16 program, includesBlockSeries, Block 10]
-
A.
supportsEventSeries
Indicates that an entity provides the necessary functionality or resources to host, manage, or accommodate a recurring series of related events.
-
B.
isSeriesOf
Indicates that one entity is a sequence or set of related items that collectively form a series associated with another entity.
-
C.
seriesIncludes
chosen
Indicates that a particular series contains or encompasses the referenced item as one of its constituent parts.
-
D.
hasEventSeries
Indicates that an entity is associated with, or participates in, a sequence of related events forming a series.
-
E.
hasSupportSeries
Indicates that one entity is backed, reinforced, or maintained by a sequence or set of supporting elements provided by another 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_69d86da09a10819082fe9797b23e4664 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e050b8154881908afe5191e6424f15 |
completed | April 16, 2026, 3 a.m. |
| PD | Predicate disambiguation | batch_69e00531e7ac8190a4190cce4f7fab4c |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:47 a.m.