Triple
T30565445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baron Ravensworth |
E777959
|
entity |
| Predicate | hasGenderForHolder |
P34342
|
FINISHED |
| Object | male-preference (historically) |
—
|
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: male-preference (historically) | Statement: [Baron Ravensworth, hasGenderForHolder, male-preference (historically)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGenderForHolder Context triple: [Baron Ravensworth, hasGenderForHolder, male-preference (historically)]
-
A.
hasGenderOfPerson
Indicates that a person is associated with a specific gender classification.
-
B.
genderOfFirstHolder
Indicates that the relationship specifies the gender of the first entity that holds or possesses something in the described context.
-
C.
genderOfTypicalHolder
chosen
Indicates the gender that is most commonly associated with or typical of the usual holder of something.
-
D.
hasGenderFormat
Indicates that something is associated with or expressed in a particular gender-related format or representation.
-
E.
hasGenderVariant
Indicates that one entity is a gender-specific form or variant of another entity.
- 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_69f2249ed41c8190b175170ecfd6e1c5 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7c29e1b848190b945c6c6120a5330 |
completed | May 3, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b6e7a881908deb96bedb2713f4 |
completed | May 3, 2026, 9:44 p.m. |
Created at: April 29, 2026, 8:21 p.m.