Triple
T36790233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | de Reynold |
E909029
|
entity |
| Predicate | nobleStatusIn |
P66828
|
FINISHED |
| Object | Canton of Fribourg |
—
|
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: Canton of Fribourg | Statement: [de Reynold, nobleStatusIn, Canton of Fribourg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nobleStatusIn Context triple: [de Reynold, nobleStatusIn, Canton of Fribourg]
-
A.
hasNobleStatus
Indicates that an entity possesses a recognized noble rank, title, or aristocratic status.
-
B.
nobleRankIn
chosen
Indicates that an entity holds a specified noble rank within a particular political or territorial jurisdiction.
-
C.
nobleRankAbove
Indicates that one entity holds a higher noble rank or title in a hierarchy than another entity.
-
D.
nobleRankOf
Indicates that one entity holds a specific noble title or rank within a hierarchical nobility system.
-
E.
hasNoble
Indicates that one entity possesses or is associated with a noble title, status, or noble individual.
- 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_69f76e7a937c81909ed7359641e670f6 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf7890008190a8bc355ff2d61c86 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4:12 p.m.