Triple
T22854425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peacekeeping Innovation Team |
E566440
|
entity |
| Predicate | hasAcronym |
P43
|
FINISHED |
| Object | PIT |
—
|
NE NERFINISHED |
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: [Peacekeeping Innovation Team, hasAcronym, PIT]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: PIT Context triple: [Peacekeeping Innovation Team, hasAcronym, PIT]
-
A.
PIT
PIT is the standard abbreviation used for the former American Basketball Association team, the Pittsburgh Pipers.
-
B.
PIT
chosen
PIT is the acronym for the Peacekeeping Innovation Team, a group focused on developing and implementing innovative solutions to enhance peacekeeping operations.
-
C.
PIT
PIT is the three-letter IATA airport code for Pittsburgh International Airport, the primary commercial airport serving the Pittsburgh, Pennsylvania metropolitan area.
-
D.
PIT
PIT is the standard three-letter abbreviation used for the NHL’s Pittsburgh Penguins in scores, standings, and statistics.
-
E.
PIT
PIT is a key Polish defense industry company specializing in the development and production of advanced military technologies and systems.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e2458750b481908a8e4cf4609cc6cf |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17ebb4ea48190b4b865e316f6a75f |
completed | April 29, 2026, 3:44 a.m. |
Created at: April 17, 2026, 3:37 p.m.