Triple
T19238476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ashkelon |
E481064
|
entity |
| Predicate | modernCityEstablished |
P34191
|
FINISHED |
| Object | 1948 |
—
|
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: 1948 | Statement: [Ashkelon, modernCityEstablished, 1948]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modernCityEstablished Context triple: [Ashkelon, modernCityEstablished, 1948]
-
A.
majorCityFounded
Indicates that one entity is a major city and the other is the date or event of its founding.
-
B.
cityFoundedAround
Indicates that a city was established approximately at, but not exactly on, a specified time or period.
-
C.
cityFoundedOn
chosen
Indicates that a city was established or officially founded on a specific date or point in time.
-
D.
modernCityBuiltAround
Indicates that a contemporary or recently developed city has been constructed encircling or surrounding a particular central feature, structure, or area.
-
E.
foundedAsMetropolis
Indicates that an entity was originally established or designated as a metropolis, typically a major or principal city.
- 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_69d8e8ccb8f48190ad420098e74fb1db |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5faef827c81909157bbcd4060dfc9 |
completed | April 20, 2026, 10:07 a.m. |
| PD | Predicate disambiguation | batch_69e4dcfae6f081909cc173cf71a5005c |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:26 p.m.