Triple
T512928
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Pennsylvania (BB-38) |
E10644
|
entity |
| Predicate | receivedBattleStars |
P15405
|
FINISHED |
| Object | 8 |
—
|
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: 8 | Statement: [USS Pennsylvania (BB-38), receivedBattleStars, 8]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: receivedBattleStars Context triple: [USS Pennsylvania (BB-38), receivedBattleStars, 8]
-
A.
hasStarOn
Indicates that one entity bears or displays a star symbol positioned on another entity.
-
B.
battledIn
Indicates that two or more entities engaged in a battle or conflict that took place at a specific location or during a particular event.
-
C.
winnerPoints
Indicates the number of points earned by the winning participant or entity in a competition or event.
-
D.
usedInBattle
Indicates that something (typically a tool, strategy, or resource) was employed or applied during a battle or combat situation.
-
E.
trophy
Indicates that one entity is a trophy awarded or possessed in relation to another entity, typically as a result of winning or achieving something.
- F. None of above. chosen
Provenance (4 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_69a2e84a0d08819087e01863fcd9abf1 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f232fa688190b08a2fe3f22c7a6e |
completed | Feb. 28, 2026, 1:48 p.m. |
| PD | Predicate disambiguation | batch_69a2f013c05481909e6dc87e7b20ebd8 |
completed | Feb. 28, 2026, 1:39 p.m. |
| PDg | Predicate description generation | batch_69a2f23214248190aa5fe1138f0f5a58 |
completed | Feb. 28, 2026, 1:48 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.