Triple
T16353381
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PIT-RADWAR |
E397112
|
entity |
| Predicate | formerlyKnownAs |
P65
|
FINISHED |
| Object | PIT |
E398120
|
NE 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: PIT | Statement: [PIT-RADWAR, formerlyKnownAs, PIT]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: PIT Context triple: [PIT-RADWAR, formerlyKnownAs, PIT]
-
A.
PIT
PIT is the standard abbreviation used for the former American Basketball Association team, the Pittsburgh Pipers.
-
B.
PIT
PIT is the standard three-letter abbreviation used for the NHL’s Pittsburgh Penguins in scores, standings, and statistics.
-
C.
PIT
chosen
PIT is a key Polish defense industry company specializing in the development and production of advanced military technologies and systems.
-
D.
PIT
PIT is the acronym for the Peacekeeping Innovation Team, a group focused on developing and implementing innovative solutions to enhance peacekeeping operations.
-
E.
piti
Piti is a traditional Azerbaijani lamb and chickpea stew slow-cooked in individual clay pots, known for its rich broth and distinctive layered serving style.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d87f26864c819088365ca381a003c2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2faccab748190b11e0808e422f2ea |
completed | April 18, 2026, 3:30 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a002db841dc8190bfe8a0d8fca1b309 |
completed | May 10, 2026, 7:03 a.m. |
Created at: April 10, 2026, 5:07 a.m.