Triple
T33289835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sudler family |
E852285
|
entity |
| Predicate | hasNameDerivedSettlement |
P53681
|
FINISHED |
| Object | Sudlersville, Maryland |
—
|
NE NERFINISHED |
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: Sudlersville, Maryland | Statement: [Sudler family, hasNameDerivedSettlement, Sudlersville, Maryland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNameDerivedSettlement Context triple: [Sudler family, hasNameDerivedSettlement, Sudlersville, Maryland]
-
A.
originalSettlementName
Indicates the name by which a settlement was originally known before any later renaming or reclassification.
-
B.
hasSettlementName
Indicates that a settlement is associated with a specific name by which it is known.
-
C.
modernNameOfServedSettlement
Indicates that the object is the current, modern name of the settlement that is or was served by the subject (e.g., a facility, infrastructure, or service).
-
D.
hasToponymicDerivatives
chosen
Indicates that a name or term serves as the source from which related place-based or toponymic names are derived.
-
E.
hasHeritageName
Indicates that an entity is associated with a specific heritage-related name, typically reflecting cultural, historical, or ancestral identity.
- F. None of above.
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_69f349660ff48190a4568803d0b89941 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fec4cffed08190b5e5e7cc0c87493e |
completed | May 9, 2026, 5:23 a.m. |
| PD | Predicate disambiguation | batch_69fec2ea7fe08190bd751b39515f69d1 |
completed | May 9, 2026, 5:15 a.m. |
Created at: May 1, 2026, 1:32 a.m.