Triple
T6295498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lie derivative |
E141121
|
entity |
| Predicate | definedAlong |
P70763
|
FINISHED |
| Object | vector field |
—
|
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: vector field | Statement: [Lie derivative, definedAlong, vector field]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definedAlong Context triple: [Lie derivative, definedAlong, vector field]
-
A.
locatedAlong
Indicates that one entity is situated adjacent to, or running beside, the length or course of another linear feature (such as a road, river, or railway).
-
B.
measuredAlong
Indicates that a measurement is taken or defined with respect to a specific direction, axis, path, or dimension.
-
C.
developedAlong
Indicates that something was created, constructed, or evolved following the course, path, or boundary of something else.
-
D.
passedAlongside
Indicates that one entity moved or traveled next to another entity along the same route or path, maintaining a roughly parallel course.
-
E.
extendsAlongCoastOf
Indicates that one entity stretches or runs parallel along the coastline of another entity.
- 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_69c008cdf2ac8190bb640c94478fb4ed |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c06439a6908190b0a8ebf426d3ca02 |
completed | March 22, 2026, 9:50 p.m. |
| PD | Predicate disambiguation | batch_69c060df0d8881908215575862ef6831 |
completed | March 22, 2026, 9:36 p.m. |
| PDg | Predicate description generation | batch_69c06284848c8190a0151ff3e8682889 |
completed | March 22, 2026, 9:43 p.m. |
Created at: March 22, 2026, 4:27 p.m.