Triple
T19157439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Propecia |
E468960
|
entity |
| Predicate | mustBeUsed |
P134650
|
FINISHED |
| Object | continuously to maintain effect |
—
|
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: continuously to maintain effect | Statement: [Propecia, mustBeUsed, continuously to maintain effect]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mustBeUsed Context triple: [Propecia, mustBeUsed, continuously to maintain effect]
-
A.
mustMeet
Indicates that one entity is required or obligated to have a meeting or encounter with another entity.
-
B.
cannotBeUsedWithout
Indicates that one entity is dependent on another such that it cannot function, operate, or be utilized unless the other entity is also present or in use.
-
C.
mustDeclare
Indicates that one entity is required or obligated to formally state, disclose, or announce something to another entity or authority.
-
D.
mustUseAssetsFor
Indicates that one entity is required to use specific assets when performing an action or fulfilling an obligation related to another entity.
-
E.
mustTell
Indicates that one entity is obligated or required to inform or disclose something to another entity.
- 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_69d8dd084ff48190ac0f8c46ee722629 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5eeba91a081909c04d61d6117da06 |
completed | April 20, 2026, 9:15 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b83d6881908e6271c620f74100 |
completed | April 19, 2026, 11:17 a.m. |
| PDg | Predicate description generation | batch_69e4bfe9ef7081908a74a57d1fc731ea |
completed | April 19, 2026, 11:43 a.m. |
Created at: April 10, 2026, 12:06 p.m.