Triple
T6833857
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Artinian module |
E157400
|
entity |
| Predicate | hasChainCondition |
P73432
|
FINISHED |
| Object | descending chain condition on submodules |
—
|
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: descending chain condition on submodules | Statement: [Artinian module, hasChainCondition, descending chain condition on submodules]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChainCondition Context triple: [Artinian module, hasChainCondition, descending chain condition on submodules]
-
A.
hasCondition
Indicates that an entity possesses, experiences, or is affected by a particular condition or state.
-
B.
hasPrecedingCondition
Indicates that one condition occurs or exists before another condition in time or sequence.
-
C.
hasNumberOfConditions
Indicates that an entity is associated with a specific count of conditions it has or is subject to.
-
D.
hasConjunction
Indicates that two or more entities are linked together by a coordinating conjunction, forming a combined or joint relationship.
-
E.
hasChainDepicted
Indicates that an entity has a chain (or chains) visually represented as part of its depiction.
- 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_69c6882c53608190b99aebef079b23bd |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d67936288190829fedc3729aadd8 |
completed | March 27, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69c6d09f90648190bc0a462c7d59de1b |
completed | March 27, 2026, 6:46 p.m. |
| PDg | Predicate description generation | batch_69c6d623aba88190a93ec9c83508c960 |
completed | March 27, 2026, 7:10 p.m. |
Created at: March 27, 2026, 2:18 p.m.