Triple
T1389457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Noetherian induction |
E29920
|
entity |
| Predicate | oftenFormulatedOn |
P28213
|
FINISHED |
| Object | partially ordered sets |
—
|
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: partially ordered sets | Statement: [Noetherian induction, oftenFormulatedOn, partially ordered sets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenFormulatedOn Context triple: [Noetherian induction, oftenFormulatedOn, partially ordered sets]
-
A.
formalizedAt
Indicates the point in time or event at which something is officially established, documented, or given formal status.
-
B.
formedAt
Indicates the time or date at which an entity was created, established, or came into existence.
-
C.
hasFormulation
Indicates that one entity is expressed, prepared, or configured in a particular form or composition defined by another entity.
-
D.
oftenPrecededBy
Indicates that one event, state, or item commonly occurs or appears before another in time or sequence.
-
E.
formulatedInYear
Indicates the specific calendar year in which something was originally created, devised, or formally established.
- 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_69a498dc92f8819094a1108f8ac90f43 |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c35ce48c81909aaad7dfa2df63fa |
completed | March 1, 2026, 10:53 p.m. |
| PD | Predicate disambiguation | batch_69a4beffcf808190ab4cd0271257ce63 |
completed | March 1, 2026, 10:34 p.m. |
| PDg | Predicate description generation | batch_69a4c2f16ae081908c92792253f3eb4b |
completed | March 1, 2026, 10:51 p.m. |
Created at: March 1, 2026, 7:59 p.m.