Triple
T37482388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord Romsey |
E931443
|
entity |
| Predicate | genderedUsage |
P15656
|
FINISHED |
| Object | male heir apparent |
—
|
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 heir apparent | Statement: [Lord Romsey, genderedUsage, male heir apparent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: genderedUsage Context triple: [Lord Romsey, genderedUsage, male heir apparent]
-
A.
genderUsage
chosen
Indicates how a particular gender is applied, referenced, or treated within a given context or system.
-
B.
genderedFormOf
Indicates that one term is a gender-specific variant or inflected form corresponding to another, more neutral or differently gendered term.
-
C.
genderImplication
Indicates that one entity’s gender suggests, constrains, or determines the possible or likely gender of another entity.
-
D.
usesGenderAccurateLanguage
Indicates that the language employed in the context correctly reflects and respects the gender identities of the entities referenced.
-
E.
genderCounterpartOf
Indicates a relationship where one entity is the corresponding counterpart of another with respect to gender.
- 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_69f76ec382248190b47844df596123c6 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba68077788190b311e027435fcf87 |
completed | May 6, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fba34c65ac8190b298f0f00d1dcc0e |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.