Triple
T14115847
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Knight Commander (AK) |
E339772
|
entity |
| Predicate | genderEquivalentTitle |
P1805
|
FINISHED |
| Object | Knight Commander |
—
|
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: Knight Commander | Statement: [Knight Commander (AK), genderEquivalentTitle, Knight Commander]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: genderEquivalentTitle Context triple: [Knight Commander (AK), genderEquivalentTitle, Knight Commander]
-
A.
officeHolderTitleWhenFemale
Indicates the specific title used for a person holding an office when that office holder is female.
-
B.
hasGenderedTitle
chosen
Indicates that an entity is associated with a title or form of address that is explicitly marked for a particular gender.
-
C.
successorTitleGender
Indicates the gender associated with the person who succeeds another in a given title or position.
-
D.
titleOrRole
Indicates that one entity serves as the title, position, or role held or described by another entity.
-
E.
patriarchalTitleType
Indicates the specific type or category of a patriarchal title held within a religious or ecclesiastical hierarchy.
- 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_69d81c6a95b481909e39111e0c1f31ee |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de6010a03c81909f5f160f8d1fa8fa |
completed | April 14, 2026, 3:41 p.m. |
| PD | Predicate disambiguation | batch_69de05b2f7e481908a9a7d40153234c0 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:22 p.m.