Triple
T5837225
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kähler form |
E129501
|
entity |
| Predicate | isLocalExpression |
P20859
|
FINISHED |
| Object | i g_{jar{k}} dz^j ∧ dar{z}^k |
—
|
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: i g_{jar{k}} dz^j ∧ dar{z}^k | Statement: [Kähler form, isLocalExpression, i g_{jar{k}} dz^j ∧ dar{z}^k]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLocalExpression
Context triple: [Kähler form, isLocalExpression, i g_{jar{k}} dz^j ∧ dar{z}^k]
-
A.
isPartOfExpression
chosen
Indicates that something functions as a component or constituent element within a larger expression.
-
B.
hasExpression
Indicates that an entity displays or possesses a particular facial or emotional expression.
-
C.
usedInExpression
Indicates that one entity (typically a term, symbol, or construct) is employed as a component within another entity that represents an expression.
-
D.
hasCoreExpression
Indicates that one entity serves as the fundamental or primary expression or representation of another entity.
-
E.
isIntrinsic
Indicates that a property or characteristic belongs inherently to an entity and does not depend on external conditions or relations.
- 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_69c0084af79c81908af128ccc29983d0 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c044ab0a048190b84be40fb13c0f50 |
completed | March 22, 2026, 7:36 p.m. |
| PD | Predicate disambiguation | batch_69c03341e5888190a5f219b6f92cb161 |
completed | March 22, 2026, 6:21 p.m. |
Created at: March 22, 2026, 3:54 p.m.