Triple
T16655840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leavenworth |
E404725
|
entity |
| Predicate | foundedAsCityIn |
P34191
|
FINISHED |
| Object | 19th 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: 19th century | Statement: [Leavenworth, foundedAsCityIn, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundedAsCityIn Context triple: [Leavenworth, foundedAsCityIn, 19th century]
-
A.
foundedAsCityBy
Indicates that a city was originally established or created by a specific person, group, or authority.
-
B.
foundedAs
Indicates the original name or form under which an organization, institution, or entity was first established.
-
C.
majorCityFounded
Indicates that one entity is a major city and the other is the date or event of its founding.
-
D.
cityFoundedOn
chosen
Indicates that a city was established or officially founded on a specific date or point in time.
-
E.
placeFounded
Indicates the location where an entity (such as an organization or institution) was originally established or founded.
- 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_69d8838b5fbc81908c6575c132b82e80 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37bfa45d8819081bf8579a7160389 |
completed | April 18, 2026, 12:41 p.m. |
| PD | Predicate disambiguation | batch_69e319b1d7f08190b5ecb4a68c636c15 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:18 a.m.