Triple
T846269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hoboken |
E18280
|
entity |
| Predicate | incorporatedAsCityOn |
P306
|
FINISHED |
| Object | 1855-03-28 |
—
|
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: 1855-03-28 | Statement: [Hoboken, incorporatedAsCityOn, 1855-03-28]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: incorporatedAsCityOn Context triple: [Hoboken, incorporatedAsCityOn, 1855-03-28]
-
A.
incorporatedAsCity
chosen
Indicates that an entity was formally established and legally recognized as a city.
-
B.
incorporatedAsTownIn
Indicates that an entity was officially established and given legal status as a town within a specified jurisdiction.
-
C.
inauguratedAsCapital
Indicates that a place was officially declared and established as the capital of a political or administrative entity.
-
D.
isFoundedOn
Indicates that one entity is established, created, or based upon another entity as its foundational source or principle.
-
E.
incorporatedAsTownship
Indicates that an area or community has been formally established and recognized as a township through a legal or governmental incorporation process.
- 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_69a4938b04208190b82e1df6b572c548 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac0a91e48190b4349ae8bb67fd90 |
completed | March 1, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69a4aa7f396c8190aa8b8dfbe0b4f732 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:38 p.m.