Triple
T7801455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moclus |
E180441
|
entity |
| Predicate | reproductionPolicy |
P63187
|
FINISHED |
| Object | state-controlled reproductive decisions |
—
|
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: state-controlled reproductive decisions | Statement: [Moclus, reproductionPolicy, state-controlled reproductive decisions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reproductionPolicy Context triple: [Moclus, reproductionPolicy, state-controlled reproductive decisions]
-
A.
reproductionRate
Indicates the frequency or speed at which an entity produces new offspring or copies of itself over a given time or condition.
-
B.
reproductionType
Indicates the mode or method by which an organism reproduces or generates offspring.
-
C.
repopulationMethod
Indicates the method or process by which a population is restored, replenished, or re-established after reduction or depletion.
-
D.
reproductionConstraint
chosen
Indicates a limitation, condition, or rule that restricts or governs how reproduction or generative processes may occur between entities.
-
E.
hasReproduction
Indicates that one entity possesses or exhibits a particular mode, process, or capability of reproduction.
- 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_69ca827e50cc8190a92a733577184938 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69caf78a6d88819093f83528fe88b182 |
completed | March 30, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69cae9111b2481909684a2d4aa4831c2 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:33 p.m.