Triple
T33525472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siding No. 2 |
E858626
|
entity |
| Predicate | usedAsSettlementNameUntil |
P145617
|
FINISHED |
| Object | early 20th 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: early 20th century | Statement: [Siding No. 2, usedAsSettlementNameUntil, early 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsSettlementNameUntil Context triple: [Siding No. 2, usedAsSettlementNameUntil, early 20th century]
-
A.
usedAsTownNameUntil
Indicates that an entity served as the official or common name of a town up to a specified point in time.
-
B.
usedAsPrimarySettlementUntil
Indicates that an entity served as the main or principal settlement for another entity up to a specified point in time.
-
C.
usedAsToponymUntil
chosen
Indicates that a name or term functioned as a place name (toponym) for a location up to a specified end time or period.
-
D.
originalSettlementName
Indicates the name by which a settlement was originally known before any later renaming or reclassification.
-
E.
usedAsCountyNameUntil
Indicates that an entity served as the official name of a county up to a specified point in time.
- 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_69f349781c6c819082c516b260efe7e2 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fe066d62b48190867df334039be786 |
completed | May 8, 2026, 3:51 p.m. |
| PD | Predicate disambiguation | batch_69fe03afde3c8190a5b9b0778d19eb1a |
completed | May 8, 2026, 3:39 p.m. |
Created at: May 1, 2026, 1:39 a.m.