Triple
T2984520
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Chicago (CA-29) |
E80589
|
entity |
| Predicate | previousPennantNumber |
P3153
|
FINISHED |
| Object | CL-29 |
—
|
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: CL-29 | Statement: [USS Chicago (CA-29), previousPennantNumber, CL-29]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousPennantNumber Context triple: [USS Chicago (CA-29), previousPennantNumber, CL-29]
-
A.
previousPennantForFranchise
Indicates that one pennant (championship title or league victory) directly preceded another for the same sports franchise in chronological order.
-
B.
pennantNumber
chosen
Indicates the identifying pennant number assigned to a ship or naval vessel.
-
C.
previousDenomination
Indicates that one entity was the earlier or former denomination (name, value, or classification) of another entity in a sequence of denominations.
-
D.
pennantNumberForFranchise
Indicates the specific pennant (league championship) number associated with a particular sports franchise.
-
E.
previousBanknoteSeries
Indicates that one banknote series directly precedes another in the chronological sequence of issued banknote series.
- 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_69ad8b15f6ac8190be5fd16a33edcb4f |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad99c65ad0819087bb4ae92ab0dc55 |
completed | March 8, 2026, 3:46 p.m. |
| PD | Predicate disambiguation | batch_69ad9611fc348190a5d17d237f653f60 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:59 p.m.