Triple
T615255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paveway series guided bombs |
E12189
|
entity |
| Predicate | firstIntroduced |
P8259
|
FINISHED |
| Object | late 1960s |
—
|
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: late 1960s | Statement: [Paveway series guided bombs, firstIntroduced, late 1960s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstIntroduced Context triple: [Paveway series guided bombs, firstIntroduced, late 1960s]
-
A.
firstAppeared
Indicates the earliest known time or context in which an entity was introduced, observed, or came into existence.
-
B.
introducedFor
Indicates that one entity was presented or brought to the attention of another entity for a specific purpose or role.
-
C.
introducedInYear
Indicates the year in which something was first introduced, launched, or made available.
-
D.
introducedDuring
chosen
Indicates that one entity was first brought into existence, use, or awareness within the time period, event, or context specified by the other entity.
-
E.
firstAnnouncedBy
Indicates that one entity is the original source or originator that publicly disclosed, reported, or made known another entity or item for the first time.
- 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_69a493309df48190a327f748e88049a6 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49e0b438881909ad515adf7a4eb79 |
completed | March 1, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69a49cfbcbf88190a854921dc531eba8 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:35 p.m.