Triple
T20805514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buras, Louisiana |
E512142
|
entity |
| Predicate | FIPSClass |
P141892
|
FINISHED |
| Object | unincorporated community |
—
|
LITERAL 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: unincorporated community | Statement: [Buras, Louisiana, FIPSClass, unincorporated community]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: FIPSClass Context triple: [Buras, Louisiana, FIPSClass, unincorporated community]
-
A.
FIPSCode
Indicates the standardized Federal Information Processing Standards (FIPS) code assigned to identify a specific geographic or administrative entity.
-
B.
FBIClassification
Indicates that an entity has a specific classification or category assigned by the FBI.
-
C.
typeOfFIU
Indicates that one entity is classified as a specific type or category of Financial Intelligence Unit (FIU) in relation to another entity.
-
D.
FIBACode
Indicates a relationship where an entity is assigned or associated with a specific FIBA (International Basketball Federation) identification code.
-
E.
usesFeistelStructure
Indicates that one entity employs a Feistel network structure as the core design of its cryptographic or transformation process.
- F. None of above. chosen
Provenance (4 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_69e0b4cc69f481908e98751e697b9df4 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c2cf1cbc819092d92625dfb107d0 |
completed | April 21, 2026, 12:20 a.m. |
| PD | Predicate disambiguation | batch_69e5c99ca55481908e8d434fa901cfd6 |
completed | April 20, 2026, 6:37 a.m. |
| PDg | Predicate description generation | batch_69e5d53c4d6881909b4d0a716fa5ed4a |
completed | April 20, 2026, 7:26 a.m. |
Created at: April 16, 2026, 12:40 p.m.