Triple
T7705310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SL(2,C) |
E174597
|
entity |
| Predicate | hasDeterminantCondition |
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(2,C), hasDeterminantCondition, determinant equal to 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDeterminantCondition Context triple: [SL(2,C), hasDeterminantCondition, determinant equal to 1]
-
A.
hasDeterminant
Indicates that one entity functions as a determiner (e.g., article, demonstrative, quantifier) specifying or limiting the reference of another entity, typically a noun or noun phrase.
-
B.
isDeterministic
Indicates that the outcome of a process or function is fully determined by its inputs, with no randomness or variation between executions.
-
C.
hasCondition
chosen
Indicates that an entity possesses, experiences, or is affected by a particular condition or state.
-
D.
determinedBy
Indicates that one entity’s state, value, or outcome is decided, controlled, or fully specified by another entity.
-
E.
hasNumberOfConditions
Indicates that an entity is associated with a specific count of conditions it has or is subject to.
- 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_69c6995b3e8c8190833108f883d5f53c |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c70402169481909b219dc5f4a64b9b |
completed | March 27, 2026, 10:26 p.m. |
| PD | Predicate disambiguation | batch_69c70165e78c8190bf6b3c34e243cb81 |
completed | March 27, 2026, 10:15 p.m. |
Created at: March 27, 2026, 4:03 p.m.