Triple
T26538858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Juda |
E671326
|
entity |
| Predicate | memorializationAt |
P18505
|
FINISHED |
| Object | Ouidah Route des Esclaves |
—
|
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: Ouidah Route des Esclaves | Statement: [Juda, memorializationAt, Ouidah Route des Esclaves]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: memorializationAt Context triple: [Juda, memorializationAt, Ouidah Route des Esclaves]
-
A.
memorialLocatedAt
chosen
Indicates that a memorial is situated or found at a specific location.
-
B.
memorialization
Indicates the act of preserving the memory or honoring the legacy of someone or something, often through a dedicated object, event, or practice.
-
C.
memorialSiteFor
Indicates that a place or structure serves as a dedicated site of remembrance or commemoration for a particular person, group, or event.
-
D.
hasMemorial
Indicates that a memorial exists in honor of, or dedicated to, a particular entity.
-
E.
commemoratedIn
Indicates that something is honored, remembered, or recognized within a particular work, event, place, or medium.
- 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_69eeb3206e748190b90c85cc81f38c91 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f657f653448190a945b4751af8507d |
completed | May 2, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69f6575ba12081909396036f78757a76 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 27, 2026, 1:40 a.m.