Triple
T24431215
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asari |
E616005
|
entity |
| Predicate | reproductionPartnerRequirement |
P63187
|
FINISHED |
| Object | any gender |
—
|
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: any gender | Statement: [Asari, reproductionPartnerRequirement, any gender]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reproductionPartnerRequirement Context triple: [Asari, reproductionPartnerRequirement, any gender]
-
A.
reproductionDependsOn
Indicates that the ability of one entity to reproduce is contingent upon the presence, condition, or actions of another entity.
-
B.
reproductionConstraint
chosen
Indicates a limitation, condition, or rule that restricts or governs how reproduction or generative processes may occur between entities.
-
C.
reproductiveRole
Indicates the specific function or part an entity plays in biological reproduction within a reproductive process or system.
-
D.
femalePartner
Indicates that one entity is the female partner in a romantic or marital relationship with the other entity.
-
E.
requiresItemForBreeding
Indicates that one entity must have or use a specific item in order for a breeding action or process with another entity to occur.
- 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_69e2d7eadb248190a867130fe45f0388 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f29782a4a0819087cb7ba399371520 |
completed | April 29, 2026, 11:42 p.m. |
| PD | Predicate disambiguation | batch_69f287d3237c819099559c00f83131d8 |
completed | April 29, 2026, 10:36 p.m. |
Created at: April 18, 2026, 2:16 a.m.