Triple
T23589669
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cartan formula |
E582440
|
entity |
| Predicate | relatesOperator |
P152818
|
FINISHED |
| Object | Lie derivative |
—
|
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: Lie derivative | Statement: [Cartan formula, relatesOperator, Lie derivative]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatesOperator Context triple: [Cartan formula, relatesOperator, Lie derivative]
-
A.
associatedWithOperator
Indicates that an entity has a relationship, connection, or linkage to a specific operator (such as a service, system, or organization) involved in its operation or management.
-
B.
involvesOperator
Indicates that a given process, action, or relationship includes or makes use of a specific operator as a participating element.
-
C.
conditionRelatesTo
Indicates that one condition is relevant, connected, or applicable to another condition or contextual factor.
-
D.
symbolicRelation
Indicates a relationship where one entity stands for, represents, or conveys meaning about another through symbols or abstract signs.
-
E.
valueRelation
Indicates a comparative or associative relationship between the values or magnitudes of two or more entities.
- F. None of above. chosen
Provenance (4 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_69e248f9e0a08190814772847003b1ff |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b03484e4819093d5c14c891f7744 |
completed | April 29, 2026, 7:16 a.m. |
| PD | Predicate disambiguation | batch_69f118c96a0081908a8ac98ef7e7e60c |
completed | April 28, 2026, 8:30 p.m. |
| PDg | Predicate description generation | batch_69f121cc494081908c987adfcde89b0e |
completed | April 28, 2026, 9:08 p.m. |
Created at: April 17, 2026, 6:41 p.m.