Triple
T38200190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Merwedeplein |
E1009032
|
entity |
| Predicate | hasAddressAssociatedWith |
P70006
|
FINISHED |
| Object | Merwedeplein 37 |
—
|
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: Merwedeplein 37 | Statement: [Merwedeplein, hasAddressAssociatedWith, Merwedeplein 37]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAddressAssociatedWith Context triple: [Merwedeplein, hasAddressAssociatedWith, Merwedeplein 37]
-
A.
associatedWithAddress
chosen
Indicates a relationship where an entity is linked or connected to a specific address.
-
B.
hasCardAssociation
Indicates that there is an established relationship or linkage between an entity and a specific card or card-related system.
-
C.
hasAddress
Indicates that an entity is associated with a specific address or location.
-
D.
leaderAssociatedWith
Indicates a relationship where a leader is connected or affiliated with a particular entity, such as an organization, group, or cause.
-
E.
bearerAssociatedWith
Indicates a relationship where a bearer (such as a person or entity holding something like an account, credential, or instrument) is linked or connected to another entity in a relevant context.
- 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_69f76dc94fcc8190bd2f55e81f9d6527 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fe7b1c506c8190869c1a22031e0571 |
completed | May 9, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69fe796b2bdc8190a86980d44008f875 |
completed | May 9, 2026, 12:01 a.m. |
Created at: May 3, 2026, 4:30 p.m.