Triple
T24036532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GL(n,ℂ) |
E595246
|
entity |
| Predicate | standardRepresentation |
P90996
|
FINISHED |
| Object | action on ℂⁿ |
—
|
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: action on ℂⁿ | Statement: [GL(n,ℂ), standardRepresentation, action on ℂⁿ]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardRepresentation Context triple: [GL(n,ℂ), standardRepresentation, action on ℂⁿ]
-
A.
standardType
Indicates that one entity is classified as the standard, canonical, or reference type for another entity or context.
-
B.
standardFormulation
Indicates that something is expressed or represented in a conventional, officially accepted, or commonly used form or version.
-
C.
formerRepresentation
Indicates that one entity previously served as the representative (e.g., legal, political, or organizational) of another entity, but no longer holds that role.
-
D.
standardReference
Indicates that one entity serves as the authoritative or canonical reference or benchmark for interpreting, validating, or comparing another entity.
-
E.
representationIn
chosen
Indicates that one entity serves as a depiction, model, or stand-in for another entity within a given context or medium.
- 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.