Triple
T21070280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Squarings (sequence) |
E519086
|
entity |
| Predicate | subsequence |
P46245
|
FINISHED |
| Object | Lightenings |
—
|
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: Lightenings | Statement: [Squarings (sequence), subsequence, Lightenings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subsequence Context triple: [Squarings (sequence), subsequence, Lightenings]
-
A.
requiresSubSequenceConstraint
Indicates that one element must occur as a subsequence within another, enforcing an ordered containment constraint between them.
-
B.
isSubsequenceOf
chosen
Indicates that one sequence can be derived from another by deleting zero or more elements without changing the order of the remaining elements.
-
C.
subsequentOrder
Indicates that one order occurs after or follows another order in sequence.
-
D.
subrange
Indicates that one value or interval lies entirely within the bounds of another value or interval.
-
E.
sequenceWith
Indicates that one entity occurs in a specific order directly before or after another entity as part of a defined sequence.
- 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_69e0b505ef108190b25dd4033e2ff7eb |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6feb7b1d081909363c8bff785164b |
completed | April 21, 2026, 4:36 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf9d71881908cd85dfc37db93ca |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:46 p.m.