Triple
T15068007
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BB-62 |
E379802
|
entity |
| Predicate | hasBattleStars |
P15405
|
FINISHED |
| Object | World War II battle stars |
—
|
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: World War II battle stars | Statement: [BB-62, hasBattleStars, World War II battle stars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBattleStars Context triple: [BB-62, hasBattleStars, World War II battle stars]
-
A.
receivedBattleStars
chosen
Indicates that an entity has been awarded one or more battle stars for participation in specific military engagements or campaigns.
-
B.
hasBattlePassIntegration
Indicates that an entity is functionally connected to or supports features of a battle pass system.
-
C.
usedInBattle
Indicates that something (typically a tool, strategy, or resource) was employed or applied during a battle or combat situation.
-
D.
hasFightingMoniker
Indicates that an entity is known by a specific nickname or title used in a fighting or combat context.
-
E.
hasKeyBattle
Indicates that an entity is associated with a major or decisive battle that is central to its history, role, or significance.
- 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_69d85cd7683881908d405c1b5d7b4f7f |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69dedeebc7e48190a86b4f0afe8844bb |
completed | April 15, 2026, 12:42 a.m. |
| PD | Predicate disambiguation | batch_69deb95a182081908fffc4402b02a394 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:02 a.m.