Triple
T36497390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hertogstraat |
E899226
|
entity |
| Predicate | hasParallelName |
P198154
|
FINISHED |
| Object | Rue Ducale |
—
|
NE NERFINISHED |
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: Rue Ducale | Statement: [Hertogstraat, hasParallelName, Rue Ducale]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParallelName Context triple: [Hertogstraat, hasParallelName, Rue Ducale]
-
A.
hasMultipleNames
chosen
Indicates that an entity is known or referred to by more than one distinct name.
-
B.
hasParallelIn
Indicates that one entity has a corresponding or analogous counterpart in another context, system, or domain.
-
C.
hasGivenNameCounterpart
Indicates that one entity is the given-name (first-name) counterpart or variant of another entity, typically linking related personal names.
-
D.
hasParallelImplementation
Indicates that one implementation of a function, process, or algorithm has a corresponding version designed to run in parallel.
-
E.
hasOfficialDualNameWith
Indicates that two entities share an officially recognized dual or joint name used in formal contexts.
- 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_69f76e5b92088190933afda3f7531dd4 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a00119d821c8190874786391b27ef23 |
completed | May 10, 2026, 5:03 a.m. |
| PD | Predicate disambiguation | batch_6a001143fb6881909ac0ae8bfea04351 |
completed | May 10, 2026, 5:01 a.m. |
Created at: May 3, 2026, 4:10 p.m.