Triple

T24036510
Position Surface form Disambiguated ID Type / Status
Subject GL(n,ℂ) E595246 entity
Predicate determinantMap P152466 FINISHED
Object det : GL(n,ℂ) → ℂˣ 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: det : GL(n,ℂ) → ℂˣ | Statement: [GL(n,ℂ), determinantMap, det : GL(n,ℂ) → ℂˣ]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: determinantMap
Context triple: [GL(n,ℂ), determinantMap, det : GL(n,ℂ) → ℂˣ]
  • A. hasDeterminantMapTo chosen
    Indicates that one entity serves as or defines the determinant (e.g., deciding factor or mapping function) that determines or maps to another entity.
  • B. determinantProperty
    Indicates that one property or factor determines, governs, or decisively influences another property or outcome.
  • C. 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.
  • D. determinant
    Indicates that a particular factor or condition has a decisive influence on the outcome, state, or behavior of another entity.
  • E. determinativeFor
    Indicates that one entity serves to uniquely identify, specify, or determine the status, interpretation, or outcome of another entity.
  • 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.