Triple
T13880248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lady President |
E333692
|
entity |
| Predicate | hasTitleHolderRequirement |
P55359
|
FINISHED |
| Object | must be a woman |
—
|
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: must be a woman | Statement: [Lady President, hasTitleHolderRequirement, must be a woman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTitleHolderRequirement Context triple: [Lady President, hasTitleHolderRequirement, must be a woman]
-
A.
hasTitleHolder
Indicates that one entity is the current or designated holder of a specific title, position, or honor associated with another entity.
-
B.
titleHolderRequirement
chosen
Indicates that a certain condition or set of conditions must be met in order for an entity to hold or retain a particular title.
-
C.
hasTitleHolderOrigin
Indicates that the origin or source location of a title holder is specified in relation to that title.
-
D.
hasTitleHolderEnchantmentBy
Indicates that a title holder possesses or is affected by an enchantment conferred or applied by a specific entity.
-
E.
hasTitleIn
Indicates that an entity holds or is associated with a specific title within a particular context, domain, or language.
- 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_69d81c5dd2d48190b7a5fc1e009de936 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de23a101488190bd790b28033d38b9 |
completed | April 14, 2026, 11:23 a.m. |
| PD | Predicate disambiguation | batch_69de05972f3881909977b4c843984f88 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:15 p.m.