Triple
T32631383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eve |
E834218
|
entity |
| Predicate | hasBiologicalDrive |
P180173
|
FINISHED |
| Object | reproductive compulsion |
—
|
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: reproductive compulsion | Statement: [Eve, hasBiologicalDrive, reproductive compulsion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBiologicalDrive Context triple: [Eve, hasBiologicalDrive, reproductive compulsion]
-
A.
hasRepressedDesireFor
Indicates that one entity harbors a hidden or unacknowledged longing or attraction toward another entity.
-
B.
hasBiologicalBasisIn
Indicates that one entity is grounded in, caused by, or dependent on the biological properties, processes, or mechanisms of another entity.
-
C.
hasSexualityCharacteristic
Indicates that an entity possesses a specific sexual orientation or sexuality-related characteristic.
-
D.
hasSex
Indicates that one entity engages in sexual activity with another entity.
-
E.
hasBiologicalRelevance
Indicates that something is pertinent to, affects, or is meaningfully connected with biological processes, systems, or functions.
- F. None of above. chosen
Provenance (4 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_69f73223675481908c1bc3208c0f5284 |
completed | May 3, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69f7317690108190b3aae2cd2e1d069e |
completed | May 3, 2026, 11:28 a.m. |
| PDg | Predicate description generation | batch_69f73221eef88190bd8905e6e9f5a586 |
completed | May 3, 2026, 11:31 a.m. |
Created at: May 1, 2026, 1:07 a.m.