Triple
T27675451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jacobi manifold |
E697764
|
entity |
| Predicate | conditionOnPair |
P61769
|
FINISHED |
| Object | [Λ,Λ] = 2E ∧ Λ (Schouten–Nijenhuis bracket) |
—
|
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: [Λ,Λ] = 2E ∧ Λ (Schouten–Nijenhuis bracket) | Statement: [Jacobi manifold, conditionOnPair, [Λ,Λ] = 2E ∧ Λ (Schouten–Nijenhuis bracket)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conditionOnPair Context triple: [Jacobi manifold, conditionOnPair, [Λ,Λ] = 2E ∧ Λ (Schouten–Nijenhuis bracket)]
-
A.
isPairOf
Indicates that two entities are associated as a matched or corresponding pair within a defined context.
-
B.
conditionWhenFound
Indicates the state or circumstances that were present at the time the entity was first discovered or observed.
-
C.
contingentOn
Indicates that the occurrence, validity, or outcome of one event or condition depends on the fulfillment or existence of another.
-
D.
containsCondition
Indicates that one entity includes, embodies, or is associated with a particular condition.
-
E.
holdsUnderCondition
chosen
Indicates that one fact, rule, or relationship remains valid only when a specified condition or set of conditions is satisfied.
- 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_69ef590d458c81909583290c3cd0478b |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f635339e888190bd1e33a0af531a38 |
completed | May 2, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69f62c1a92648190835a2c5250d8c758 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 2:43 p.m.