Triple
T10300730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sint-Omaars |
E241619
|
entity |
| Predicate | ligtAan |
P92989
|
FINISHED |
| Object | riviertje Aa |
—
|
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: riviertje Aa | Statement: [Sint-Omaars, ligtAan, riviertje Aa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ligtAan Context triple: [Sint-Omaars, ligtAan, riviertje Aa]
-
A.
verwantAan
Indicates that one entity is related or connected to another, typically through some form of kinship, association, or conceptual similarity.
-
B.
aka
Indicates that one entity is also known by an alternative name or alias that refers to the same thing.
-
C.
ally
Indicates a cooperative relationship in which one entity supports, assists, or aligns with another, often for mutual benefit or a shared goal.
-
D.
lays
Indicates that one entity deposits or places something, typically eggs or objects, onto a surface or in a location.
-
E.
over
Indicates that one entity is positioned higher than and extending across or above another entity, often covering or spanning it.
- F. None of above. chosen
Provenance (4 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_69d381aaafc08190af475ef58dc16aba |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d2eefe8881908a672c4dca7657ca |
completed | April 7, 2026, 9:48 a.m. |
| PD | Predicate disambiguation | batch_69d4d1f35e548190be3b4d92d65d2d20 |
completed | April 7, 2026, 9:44 a.m. |
| PDg | Predicate description generation | batch_69d4d29d7cf08190acd70cee634c5cdb |
completed | April 7, 2026, 9:47 a.m. |
Created at: April 6, 2026, 11:44 a.m.