Triple
T26527502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marquis of Namur |
E670731
|
entity |
| Predicate | titleOver |
P179779
|
FINISHED |
| Object | County of Namur |
—
|
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: County of Namur | Statement: [Marquis of Namur, titleOver, County of Namur]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleOver Context triple: [Marquis of Namur, titleOver, County of Namur]
-
A.
titleThrough
Indicates a relationship where one entity holds or is identified by a specific title by means of, or via the mediation of, another entity or context.
-
B.
title
Indicates that one entity serves as the formal name or designation of another entity.
-
C.
titleStart
Indicates that one entity’s title begins with the text or substring represented by the other entity.
-
D.
titleAffirms
Indicates that a title explicitly asserts, confirms, or supports the truth or validity of a particular claim, idea, or relationship.
-
E.
titleVariant
Indicates that one title is an alternative or variant form of another title referring to the same work or entity.
- 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_69eeb31ea1e08190b9ff43cf9bc25bf8 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f727afd5d88190ad48735cd1b32787 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72737c42c8190a3f781a5e98868ff |
completed | May 3, 2026, 10:45 a.m. |
| PDg | Predicate description generation | batch_69f727ad9ff88190ba8069dd48b2e98f |
completed | May 3, 2026, 10:47 a.m. |
Created at: April 27, 2026, 1:33 a.m.