Triple
T20813241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Littleton Public Schools |
E512366
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | LPS |
—
|
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: LPS | Statement: [Littleton Public Schools, abbreviation, LPS]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: LPS Context triple: [Littleton Public Schools, abbreviation, LPS]
-
A.
LPS
chosen
LPS is the commonly used abbreviation for Littleton Public Schools, a public school district serving the Littleton, Colorado area.
-
B.
LPSJ
LPSJ is the ICAO airport code for São Jorge Airport, which serves the island of São Jorge in Portugal’s Azores archipelago.
-
C.
LRPS
LRPS is a distinction awarded by the Royal Photographic Society to photographers who demonstrate a high standard of technical competence and creative ability.
-
D.
LPPS
LPPS is the ICAO airport code for Porto Santo Airport, which serves the island of Porto Santo in Portugal’s Madeira archipelago.
-
E.
LAP
LAP is the ICAO airline designator used to identify LATAM Airlines Paraguay in international aviation operations.
- 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_69e0b4cd25088190b48ca9700cd24efc |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c2d415688190b66adc44d4df9bbb |
completed | April 21, 2026, 12:20 a.m. |
Created at: April 16, 2026, 12:40 p.m.