Triple
T15619705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Freising |
E375515
|
entity |
| Predicate | vehicleRegistrationCode |
P1173
|
FINISHED |
| Object | FS |
E794729
|
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: FS | Statement: [Freising, vehicleRegistrationCode, FS]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: FS Context triple: [Freising, vehicleRegistrationCode, FS]
-
A.
FS
chosen
FS is the vehicle registration code used on license plates for vehicles registered in the district of Freising in Bavaria, Germany.
-
B.
FSV
FSV is the commonly used abbreviation for FSV Zwickau, a German football club based in Zwickau, Saxony.
-
C.
SFS
SFS is a renowned Georgetown University school specializing in international affairs, diplomacy, and global policy education.
-
D.
SFS
SFS is the commonly used abbreviation for the San Francisco Symphony, a major American orchestra based in San Francisco, California.
-
E.
SFS
SFS is a spatial feature standard that defines how geographic features and their properties are modeled and accessed in geospatial information systems.
- 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_69d85ccf2794819096cda4cbcb02d478 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04e997ce481909b2f10d25705fbc6 |
completed | April 16, 2026, 2:51 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff5f3b643c819093230df6cfe440b9 |
completed | May 9, 2026, 4:22 p.m. |
Created at: April 10, 2026, 4:13 a.m.