Triple
T9068359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LCGFT |
E217299
|
entity |
| Predicate | hasAbbreviation |
P43
|
FINISHED |
| Object | LCGFT |
E217299
|
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: LCGFT | Statement: [LCGFT, hasAbbreviation, LCGFT]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: LCGFT Context triple: [LCGFT, hasAbbreviation, LCGFT]
-
A.
LCGFT
chosen
LCGFT is the standard controlled vocabulary developed by the Library of Congress for describing the genre and form of library and archival materials.
-
B.
LCG
LCG is the National Rail station code assigned to Lochgelly railway station in Fife, Scotland.
-
C.
LCF
LCF is an abbreviation used for Kouri-Vini, the Louisiana Creole language spoken primarily in Louisiana’s Creole communities.
-
D.
LGC
LGC is the three-letter IATA airport code for LaGrange–Callaway Airport in LaGrange, Georgia, United States.
-
E.
LCDGT
LCDGT is the standard controlled vocabulary developed by the Library of Congress to describe demographic characteristics of creators and contributors in library and archival metadata.
- 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_69ca83d5a7f48190b16c1e59bd43ede0 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc94bf4f2881908c881e6ee7203994 |
completed | April 1, 2026, 3:45 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cffddc5c288190b18c2ae1aece4ed6 |
completed | April 3, 2026, 5:50 p.m. |
Created at: March 30, 2026, 7:11 p.m.