Triple
T20282546
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Dunbar (1338) |
E503185
|
entity |
| Predicate | hasGenderOfKeyCommander |
P39348
|
FINISHED |
| Object | female |
—
|
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: female | Statement: [Battle of Dunbar (1338), hasGenderOfKeyCommander, female]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGenderOfKeyCommander Context triple: [Battle of Dunbar (1338), hasGenderOfKeyCommander, female]
-
A.
hasGenderRole
Indicates that an entity is associated with, or expected to perform, a particular socially defined gender-based role or set of behaviors.
-
B.
hasGenderOfPerson
chosen
Indicates that a person is associated with a specific gender classification.
-
C.
hasGenderSystem
Indicates that an entity employs or is characterized by a particular system for categorizing gender.
-
D.
governsGender
Indicates that one entity determines or constrains the gender classification or gender-related properties of another entity.
-
E.
hasGenderConvention
Indicates that there is an established or customary way of assigning or expressing gender within a given context, system, or culture.
- 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_69e0b4b0e79c8190bd61f22ef1329fa8 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6768f86448190842389a98b93a918 |
completed | April 20, 2026, 6:55 p.m. |
| PD | Predicate disambiguation | batch_69e55b1e5e1c8190ba8a5544b1db9e1d |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 16, 2026, 10:40 a.m.