Triple
T33579708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cartier divisor |
E860118
|
entity |
| Predicate | effectiveIf |
P142355
|
FINISHED |
| Object | locally given by regular function |
—
|
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: locally given by regular function | Statement: [Cartier divisor, effectiveIf, locally given by regular function]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: effectiveIf Context triple: [Cartier divisor, effectiveIf, locally given by regular function]
-
A.
effectiveWithin
Indicates that one entity (such as a rule, condition, or effect) is valid, applicable, or in force only during a specified time period or within a defined contextual boundary.
-
B.
effectiveFor
Indicates that one entity successfully produces the intended effect, benefit, or desired outcome for another entity or condition.
-
C.
conditionalEffect
chosen
Indicates that one event, state, or action occurs or holds only if a specified condition is met.
-
D.
tookEffect
Indicates that a change, rule, condition, or event became active, operative, or started producing its intended consequences.
-
E.
effectIfRatified
Indicates that a particular effect or outcome will occur if and when an agreement, decision, or measure is formally ratified.
- 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_69f3497d37848190afcbb5ef3f5c7376 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fcf1b3d9a08190850b388308656266 |
completed | May 7, 2026, 8:10 p.m. |
| PD | Predicate disambiguation | batch_69fcf0226d8c8190b23dceafb1794995 |
completed | May 7, 2026, 8:03 p.m. |
Created at: May 1, 2026, 1:40 a.m.