Triple
T17351086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Darby, Pennsylvania |
E421812
|
entity |
| Predicate | hasHistoricSettlementDate |
P60311
|
FINISHED |
| Object | 17th century |
—
|
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: 17th century | Statement: [Darby, Pennsylvania, hasHistoricSettlementDate, 17th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricSettlementDate Context triple: [Darby, Pennsylvania, hasHistoricSettlementDate, 17th century]
-
A.
hasSettlementHistory
chosen
Indicates that an entity has a documented history of human settlement or habitation in relation to another entity (such as a place or time period).
-
B.
hasSettlementContinuitySince
Indicates that a settlement has existed continuously at a location since a specified point in time.
-
C.
settledDate
Indicates the date on which a transaction, obligation, or agreement is fully completed and finalized.
-
D.
hasSettlementAround
Indicates that a settlement is located in the surrounding area of a specified place or feature.
-
E.
hasSettlementOnBanks
Indicates that a settlement is located on or along the banks of a geographic feature such as a river, lake, or coastline.
- 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_69d889d520008190a26917a95bf1c2ea |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a2ca0708190aae8306ec3a6f2a7 |
completed | April 19, 2026, 2:13 a.m. |
| PD | Predicate disambiguation | batch_69e3b02662d08190a07d0fb5c04b6f33 |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:44 a.m.