Triple
T1249008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pascal's triangle |
E26830
|
entity |
| Predicate | parityPattern |
P8034
|
FINISHED |
| Object | mod 2 pattern forms Sierpiński triangle |
—
|
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: mod 2 pattern forms Sierpiński triangle | Statement: [Pascal's triangle, parityPattern, mod 2 pattern forms Sierpiński triangle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parityPattern Context triple: [Pascal's triangle, parityPattern, mod 2 pattern forms Sierpiński triangle]
-
A.
pattern
chosen
Indicates that one entity exhibits, follows, or is characterized by a particular recurring form, structure, or arrangement associated with another entity.
-
B.
parityWith
Indicates that two entities share the same parity, such as both being even or both being odd.
-
C.
kitPattern
Indicates the design or visual pattern featured on a team's kit or uniform.
-
D.
hatPattern
Indicates that one entity has a hat characterized by a specific pattern or design.
-
E.
parity
Indicates that two quantities share the same evenness or oddness, or more generally that they have equivalent status or value in a given context.
- 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_69a49487a9c48190ba9b05348fd1b53f |
completed | March 1, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69a4bf83b32c81908648e5748b897247 |
completed | March 1, 2026, 10:36 p.m. |
| PD | Predicate disambiguation | batch_69a4bb6b075881908e867c25b5080e25 |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:47 p.m.