Triple
T32636662
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leviathan |
E834360
|
entity |
| Predicate | genderInSomeSources |
P95195
|
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: [Leviathan, genderInSomeSources, female]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: genderInSomeSources Context triple: [Leviathan, genderInSomeSources, female]
-
A.
genderVariants
Indicates that one entity is a gender-related variant or alternative form of another (e.g., masculine/feminine/neuter versions of the same base entity).
-
B.
genderSpecificity
Indicates whether the relationship or action applies specifically to a particular gender or is gender-neutral.
-
C.
genderConfiguration
Indicates how the genders of the involved entities are arranged or combined within a particular relationship or context.
-
D.
genderVariant
Indicates that an entity’s gender identity or expression differs from traditional or expected norms associated with their assigned sex or gender.
-
E.
genderIdentityInSources
chosen
Indicates that the gender identity of an entity is recorded or referenced in one or more information sources.
- 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_69f3492dc2308190a88c6e30a3f3f576 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6c775d6188190b236fc4f89a11b61 |
completed | May 3, 2026, 3:56 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f617c08190a70ba880210f908c |
completed | May 3, 2026, 3:41 a.m. |
Created at: May 1, 2026, 1:07 a.m.