Triple
T24036547
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SL(n,ℂ) |
E595247
|
entity |
| Predicate | hasConditionOnElements |
P1255
|
FINISHED |
| Object | determinant equal to 1 |
—
|
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: determinant equal to 1 | Statement: [SL(n,ℂ), hasConditionOnElements, determinant equal to 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConditionOnElements Context triple: [SL(n,ℂ), hasConditionOnElements, determinant equal to 1]
-
A.
hasCondition
chosen
Indicates that an entity possesses, experiences, or is affected by a particular condition or state.
-
B.
containsCondition
Indicates that one entity includes, embodies, or is associated with a particular condition.
-
C.
hasNumberOfConditions
Indicates that an entity is associated with a specific count of conditions it has or is subject to.
-
D.
hasChainCondition
Indicates that one entity is subject to, or satisfies, a specified chain condition imposed or characterized by another entity.
-
E.
hasElementType
Indicates that something is composed of or contains elements that are of a specified type.
- 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_69e288bf45f08190a1b6ed8cd0b9e86b |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d8d43884819093e9207a99ae2a70 |
completed | April 29, 2026, 10:09 a.m. |
| PD | Predicate disambiguation | batch_69f1764345388190a3102b62ddb729b4 |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 9:56 p.m.