Triple
T25645191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Javelin |
E642940
|
entity |
| Predicate | serviceBrandIntroduced |
P34842
|
FINISHED |
| Object | 2009 |
—
|
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: 2009 | Statement: [Javelin, serviceBrandIntroduced, 2009]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceBrandIntroduced Context triple: [Javelin, serviceBrandIntroduced, 2009]
-
A.
serviceBrand
chosen
Indicates that one entity is the brand under which a particular service is offered or marketed by another entity.
-
B.
serviceIntroduced
Indicates that a particular service has been launched, made available, or brought into operation at a certain time or context.
-
C.
introducedUnderBrand
Indicates that one entity was launched, released, or brought to market using the branding or brand identity of another entity.
-
D.
introducedAsBrandFor
Indicates that one entity was presented or launched to the public specifically as the brand representing another entity.
-
E.
supportsBrand
Indicates that one entity endorses, promotes, or is compatible with a particular brand.
- 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_69e77e7ce28081908b08d65ee6e5c8be |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a731508190bb0c8c2462eba224 |
completed | May 2, 2026, 7:33 p.m. |
Created at: April 21, 2026, 5:51 p.m.