Triple
T22977295
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Excellent Cadaver |
E571360
|
entity |
| Predicate | hasFounderGender |
P51361
|
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: [Excellent Cadaver, hasFounderGender, female]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFounderGender Context triple: [Excellent Cadaver, hasFounderGender, female]
-
A.
founderGender
chosen
Indicates the gender identity of the person who founded an organization, company, or entity.
-
B.
hasFounderName
Indicates that an entity has a founder whose personal name is given by the associated value.
-
C.
possiblyFoundedBy
Indicates that an entity may have been founded or established by another entity, but this founding relationship is uncertain or not definitively confirmed.
-
D.
genderOfEponym
Indicates the gender of the person after whom something (such as a place, object, or concept) is named.
-
E.
genderOfFirstHolder
Indicates that the relationship specifies the gender of the first entity that holds or possesses something in the described context.
- 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_69e245b3c50481908bb3741ec9f40862 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18292f3788190ab4e9d559e0070c8 |
completed | April 29, 2026, 4:01 a.m. |
| PD | Predicate disambiguation | batch_69ef3b9101f48190a06c69dff26c6441 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:48 p.m.