Triple
T33890345
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | County of Chartres |
E868741
|
entity |
| Predicate | associatedNobilityTitleRank |
P67819
|
FINISHED |
| Object | duchy |
—
|
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: duchy | Statement: [County of Chartres, associatedNobilityTitleRank, duchy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedNobilityTitleRank Context triple: [County of Chartres, associatedNobilityTitleRank, duchy]
-
A.
associatedNobleTitle
Indicates that an entity is linked to or bears a particular noble or aristocratic title.
-
B.
associatedNobleRank
chosen
Indicates that an entity is linked to or holds a particular noble rank or title.
-
C.
nobleTitleOrStatus
Indicates that one entity holds, claims, or is associated with a particular noble rank, title, or social status in relation to another entity.
-
D.
nobilityTitleType
Indicates the specific kind or category of noble rank or title associated with an entity.
-
E.
aristocraticTitleStatus
Indicates the status or condition of an entity’s aristocratic or noble title (e.g., whether and how the title is held, recognized, or used).
- 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_69f34996761c8190864e42f7c9cf215b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037e0953908190b2930b3c06a40129 |
completed | May 12, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_6a0379f6c3308190b954f7810214ceed |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:48 a.m.