Triple
T5857940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sussex County |
E130199
|
entity |
| Predicate | federalStateCode |
P67526
|
FINISHED |
| Object | 10 (Delaware) |
—
|
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: 10 (Delaware) | Statement: [Sussex County, federalStateCode, 10 (Delaware)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: federalStateCode Context triple: [Sussex County, federalStateCode, 10 (Delaware)]
-
A.
federalStateOfGermany
Indicates that one entity is a federal state (Bundesland) that is a constituent state within the country of Germany.
-
B.
cantonCode
Indicates the specific administrative canton identifier associated with an entity or location.
-
C.
codeForSovereignState
Indicates that an entity serves as a code or coded identifier that officially represents a particular sovereign state.
-
D.
federalRegion
Indicates that an entity is located within, administered by, or associated with a specific federal region or federal-level administrative division.
-
E.
confederationCode
Indicates the code that identifies the confederation or overarching organizational grouping to which an entity belongs.
- 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_69c0084f3bb08190a7720f55f7aa4252 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c044ab0a048190b84be40fb13c0f50 |
completed | March 22, 2026, 7:36 p.m. |
| PD | Predicate disambiguation | batch_69c03345ca0c819081c81148d054fed2 |
completed | March 22, 2026, 6:21 p.m. |
| PDg | Predicate description generation | batch_69c044a9c4f0819081b8c196932883f6 |
completed | March 22, 2026, 7:36 p.m. |
Created at: March 22, 2026, 3:56 p.m.