Triple
T2594225
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christoffel symbols |
E58190
|
entity |
| Predicate | dependOn |
P38982
|
FINISHED |
| Object | choice of coordinates |
—
|
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: choice of coordinates | Statement: [Christoffel symbols, dependOn, choice of coordinates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dependOn Context triple: [Christoffel symbols, dependOn, choice of coordinates]
-
A.
dependency
chosen
Indicates that one entity relies on, is conditioned by, or cannot function or exist properly without another entity.
-
B.
contingentOn
Indicates that the occurrence, validity, or outcome of one event or condition depends on the fulfillment or existence of another.
-
C.
doesNotDependOn
Indicates that one entity’s state, behavior, or outcome is completely independent of, and not influenced or determined by, another entity.
-
D.
hasDependency
Indicates that one entity relies on or requires another entity in order to function, exist, or be fulfilled.
-
E.
distanceSupportDependsOn
Indicates that the level or type of support provided is contingent on the physical or relational distance between the involved entities.
- 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_69ab4ac14040819098b13f4a27d5c8ff |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abd427f58c8190af1c1a9724158c96 |
completed | March 7, 2026, 7:30 a.m. |
| PD | Predicate disambiguation | batch_69abd0d344988190a18dd93b13e002e6 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:49 p.m.