Triple
T1347045
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haarlem |
E28594
|
entity |
| Predicate | hasCityRightSince |
P15548
|
FINISHED |
| Object | 1245 |
—
|
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: 1245 | Statement: [Haarlem, hasCityRightSince, 1245]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCityRightSince Context triple: [Haarlem, hasCityRightSince, 1245]
-
A.
hasMetropolitanAuthorityOver
Indicates that one entity holds official governing or administrative authority over a metropolitan area or region associated with another entity.
-
B.
historicalRightGranted
chosen
Indicates that a right or privilege was formally granted to an entity at some point in the past.
-
C.
hasLegalRight
Indicates that an entity possesses an officially recognized legal entitlement or permission to perform an action or hold a claim regarding another entity.
-
D.
hasHistoricCity
Indicates that an entity possesses, contains, or is associated with a city recognized for its historical significance.
-
E.
hasVoivodeshipRights
Indicates that an entity possesses the legal status, privileges, or jurisdictional authority associated with a voivodeship (a regional administrative unit).
- 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_69a49854eb3481908c7d56b2e449a290 |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c2406c488190b2c04d54d9c5e94c |
completed | March 1, 2026, 10:48 p.m. |
| PD | Predicate disambiguation | batch_69a4bef5857c81909ae984feb85a26ca |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:56 p.m.