Triple
T5425785
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Picard iteration |
E121358
|
entity |
| Predicate | definesSequence |
P41558
|
FINISHED |
| Object | sequence of approximate solutions |
—
|
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: sequence of approximate solutions | Statement: [Picard iteration, definesSequence, sequence of approximate solutions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesSequence Context triple: [Picard iteration, definesSequence, sequence of approximate solutions]
-
A.
letterSequence
Indicates that one sequence of letters directly follows or is ordered in relation to another within a larger string or alphabetic arrangement.
-
B.
featuresSequence
chosen
Indicates that one entity presents or contains another entity as an ordered sequence of features or elements.
-
C.
isSeriesOf
Indicates that one entity is a sequence or set of related items that collectively form a series associated with another entity.
-
D.
programSequence
Indicates that one program or step occurs in a specific order directly before or after another within a defined sequence.
-
E.
sequencerType
Indicates the specific kind or category of sequencer associated with or used in relation to an entity.
- 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_69bd463b58d88190b258261573de9e91 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd8911a7348190ad9378a248190f07 |
completed | March 20, 2026, 5:51 p.m. |
| PD | Predicate disambiguation | batch_69bd846b8bdc81909dcdc2a3084226f2 |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:06 p.m.