Triple
T12143164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ustka |
E289241
|
entity |
| Predicate | carPlates |
P1173
|
FINISHED |
| Object | GSL |
E142546
|
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: GSL | Statement: [Ustka, carPlates, GSL]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: GSL Context triple: [Ustka, carPlates, GSL]
-
A.
GSL
chosen
GSL is the vehicle registration code assigned to cars registered in a specific district of Poland’s Pomeranian Voivodeship.
-
B.
gauss
The gauss is a unit of magnetic flux density in the centimeter–gram–second (CGS) system, commonly used in physics to measure the strength of magnetic fields.
-
C.
GIL
GIL is the IATA airport code for Gilgit Airport, which serves the city of Gilgit in northern Pakistan.
-
D.
GSO
GSO is a regional standards body that develops and harmonizes technical regulations and standards for the Gulf Cooperation Council member states.
-
E.
GSO
GSO is the three-letter FAA airport code for Piedmont Triad International Airport serving the Greensboro, North Carolina area.
- 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_69d6ab4c6710819097a9d228382dde43 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d915aacaa08190b31f54e230334406 |
completed | April 10, 2026, 3:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f5f69501348190a9ac090c7db37c20 |
completed | May 2, 2026, 1:05 p.m. |
Created at: April 8, 2026, 9:49 p.m.