Triple
T26006753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Euclidean algorithm for polynomials |
E646780
|
entity |
| Predicate | applicableOver |
P36369
|
FINISHED |
| Object | fields |
—
|
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: fields | Statement: [Euclidean algorithm for polynomials, applicableOver, fields]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: applicableOver Context triple: [Euclidean algorithm for polynomials, applicableOver, fields]
-
A.
appliesOver
chosen
Indicates that one entity’s effect, rule, or condition extends across or is valid for a specified range, domain, or set of entities.
-
B.
appliesTo
Indicates that something is relevant, valid, or has effect in relation to a particular entity, case, or context.
-
C.
canBeUsedOver
Indicates that one entity is suitable or valid for use in place of, or in relation to, another entity.
-
D.
appliesAlsoTo
Indicates that a condition, rule, or characteristic that applies to one entity is additionally applicable to another entity.
-
E.
appliesAt
Indicates that an action, rule, or condition is relevant to or in effect at a specific location, context, or point in time.
- 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_69e77e89d5848190b54352cdb74f6029 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca204148190850a3dc325bc07b7 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 22, 2026, 9 a.m.